-
Notifications
You must be signed in to change notification settings - Fork 486
Error running documentation as a npm script in packages.json #339
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
Comments
don't you forget |
I left out a lot out of package.json I have a lot more dependencies, and I have a webpack build script as well. I just don't think those are necessary to show the issue. |
i mean shouldn't command be like: |
documentation specifies all versions of babel it needs: https://github.com/documentationjs/documentation/blob/master/package.json#L11-L17 - it's very likely that this is a |
@newjam any more details? I'm not finding any ways to debug this issue. Did the npm install go cleanly? |
@tmcw thanks for looking into this. I just tried this again, with |
* Add example of using guards with case expression * Apply review feedback
I don't want to install
documentation
globally, but install it as a project dev dependency, so new developers only need to install the node dependency. I can then run documentation from npm by specify a script inpackages.json
(I abridged it to only show relevant details)I can then run the documentation script.
There seems to be a version conflict here. Like
documentation
requires a certain version ofbabel
that has thecanCompile
method. However, it doesn't seem to verify that the version is correct. I don't know if there even is a fix. I just wanted to point out some friction when I tried to integrate this into my project.The text was updated successfully, but these errors were encountered: