-
-
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
Docz does not work if project uses an old version of lodash #1313
Comments
This is also an issue with An easy solution could be to export a |
Hey @petejodo Thanks for reporting this issue ! I took your suggestion and made docz-utils export lodash/get and lodash/fp/mergeWith. It should be released with the next docz release. Meanwhile, you can try it out with : |
confirmed that this works with docz@2.3.0-alpha.1. Thanks for the quick response and fix @rakannimer! |
I have this issue with docz 2.3.1 and fresh install.
Funny that I actually can see |
Bug Report
Describe the bug
When a project depends on an old version of lodash, e.g.
v3.10.1
, then running docz commands likedocz:dev
fail because lodash does not contain alodash/fp
module. This is because the config filegatsby-config.js
located in the project root's.docz/
directory resolves to the project's installed lodash version.On top of that, editing the config to not use
lodash/fp
doesn't work because the validating of the config file overwrites any changes, causing it to error regardless.A clear and concise description of what the bug is.
To Reproduce
Please try to build a small repo with a repro of your problem and provide a link to it.
Doing that allows more people to quickly help you.
If you can't provide a repo then provide clear steps describing how to reproduce the issue.
create-react-app my-docz-app && cd my-docz-app
npm i --save lodash@3.10.1 docz
"docz:dev": "docz dev"
as script topackage.json
npm run docz:dev
Expected behavior
This shouldn't crash because I'm using some unexpected version of lodash.
Environment
Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.
The text was updated successfully, but these errors were encountered: