-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different behaviours with yarn and npm installs #276
Comments
It looks like the developers have chosen Yarn as it package manager, also, the whole documentation tells you to use it. As you can see here managing both might be cumbersome and the two files (package-lock.json and yarn.lock) might get out-of-sync.
If you are still thinking that a project should support both package managers, this is a message that Yarn throws into the console when you try to install a project's dependencies with Yarn and there is a
Hope it helps. |
looks like this issue is also related to #247 |
@lttb I suspect so. I had thought I'm going to close this, as I don't think there's an appetite for figuring out how to make this work the same with |
I think it should be kept open & looked into, seems pretty weird to require yarn for correct functionality without stating that anywhere. After all, the docz documentation only states the following (bolded bit added by me):
|
Bug Report
Describe the bug
When installing via
npm
, the TOC / submenu items don't appear in the docz output, but when installing viayarn
, they do appear. I'm sure this is related to issues such as #206.I'm using version 0.10.3 but during my debugging I've also seen it on older versions. I've been able to reliably reproduce it using the steps below.
To Reproduce
npm install
, anddocz dev
yarn install
anddocz dev
If yarn installs, everything's groovy. If npm installs, things are broken.
Expected behavior
NPM and Yarn should install the same packages, or at least the NPM one works properly.
Environment
Additional context/Screenshots
I assume this is due to package versions way down the chain being resolved differently, but I have no idea where to start.
The text was updated successfully, but these errors were encountered: