Open MorrisonCole opened 6 days ago
https://github.com/facebook/docusaurus/pull/10391 added a peer dependency of core on MDX, so all dependents of core must also peerly depend on MDX. I don't fancy this idea especially since the core should be content-agnostic. @slorber is it possible for the core to expose a plugin API that injects module aliases for bundlers?
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
A fair few core packages have unsatisfied peer dependencies with a fresh project on
3.6.1
. This is most obvious with something likeyarn 3.5.0
, but also reproducable withpnpm
andauto-install-peers=false
.Full set of warnings below.
Reproducible demo
https://github.com/MorrisonCole/docusaurus-peer-dependencies-repro/
Steps to reproduce
npm init docusaurus@latest
classic
TypeScript
yarn
is available withcorepack enable
yarn
from the new project. Depending on the version, different warnings will be printed at this time, but you can see all peer warnings withyarn explain peer-requirements
.Expected behavior
No
YN0002
warnings / missing peers.Actual behavior
Fair few missing peers, e.g., with (
yarn set version 3.5.0
):Your environment
3.6.1
130.0.6723.117
, Nodev20.10.0
Self-service