-
Notifications
You must be signed in to change notification settings - Fork 71
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
Error with adding script through cli #94
Comments
Thanks @jonniebigodes. I guess we need to use |
@ndelangen i see that a pr is up. Thank you very much for the time and effort you put into this issue. |
@ndelangen sorry to bother you, but it seems that this is still a issue. While working on the intro to storybook with ember, upon reaching the testing section the behaviour presented itself again. I thought that it could be a cached version. So i cleared the npm cache, recreated the project once again and added the dependency and it was still showing the same script. Feel free to provide feedback |
We'll publish the new version with this fix next weekend @jonniebigodes, sorry for the delay. |
@ndelangen no problem, once again thank you for the time it was put into this. I'll be on the lookout and then when it's released i'll update things on my side. |
While working on a pr on the learnstorybook repo i was following the steps of the tutorial up until the test section all is good up until the i'm executing the
npx chromatic --app-code=<app-code>
command. I let it run to completion, only when the process finishes and i'm presented with the following:As you can see i selected the yes (y) option to allow the cli to create a script to my project.
Now checking the
package.json
file i'm presented with the following:I'm just leaving in the necessary information, namely the devDependencies and the scripts available.
Now as me or any other user that goes with this route as soon as he/she makes any change and tries to run the script the following will be displayed:
This is not the first time this has popped up for me. while i was doing some work on another piece of documentation this issue presented itself, but i thought it might be a fluke, probably the package manager acting up or something on that nature.
Is this intended behaviour or something is amiss?
To add a bit more of context, i'm running on a windows 10 machine. Should anymore information be necessary i'm more than happy to push the code i'm using to a repo on GitHub.
Feel free to provide feedback
The text was updated successfully, but these errors were encountered: