Some dependency seems to get skipped and unable to find (chokidar) #629
Comments
|
Thanks for the report! Can you please post the output of |
|
@kittens Actually, I think I found a clue. When I install Below is output of |
|
can confirm the same issue on a project with more packages. I get the same behavior running both edit: Also forgot to add this is on |
|
I'm getting a similar issue with |
|
As a quik fix |
|
cc @TheLarkInn @bebraw @sokra @SpaceK33z to track this. |
|
I ran into the same issue.
|
|
I had same experience as OP, chokidar is missing from node_modules but present in the lock |
|
+1 with chokidar package |
|
I'm experiencing the same issue trying to work on https://github.com/hownowbrowncow/material-timepicker so if you want something to test against there is that. Running Let me know what else I can provide to help with the issue. |
|
I also found some problems with fsevents library, having the solution above After clean install I does not see So node takes 100+% cpu as But if I run |
|
Same problem but with graceful-fs. I can use the resolved URL in the yarn.lock file to successfully download and extract it into node_modules manually. |
|
Not sure if it's related, but I'm getting same problems just when running |
|
I have same problem. When I try to install packages with production flag |
|
Looks like @andreysdr's and my comment should go to #761 |
|
I believe that #670 helps narrow down a root cause - optional dependencies with native modules. |
|
+1 for chokidar package missing using webpack (watchpack). |
|
Yet installing it manually does not solve the problem:/ |
|
It seems to be fixed for me. Node isn't at 100 % anymore. |
|
@steida can you confirm that this was fixed by using a new release of yarn? seems like there was no pull request or official response. |
|
As mentioned in the issue I believe this to be a duplicate of, the issue should be resolved via #809, which is committed in 558aa38 and available in v0.16.0. |
|
@shepmaster thanks for the detailed response. I just updated to yarn 0.16.1 and the issue is indeed fixed. I think this issue can be safely closed. |
|
Wasn't fixed for me as of 0.16, haven't been able to test with 0.16.1 yet. |
|
This was fixed for me in 0.16 as well. Curious that its still not working for @outdooricon. |
|
I'm using 0.16.1 and am seeing this issue. Experiencing a 2x jump in Webpack build times. |
|
Now works for me with 0.16.1! |
|
I'm seeing a similar issue on 0.16.1 and socket.io related dependencies (like json3) |
|
Back in 0.17.0 😕 |
|
I opened #1838, I guess it's the same issue? |
|
Facing this issue in 0.17.8 with |
|
I updated to 0.17.9 and it didn't seem fixed because my CPU still ran away. Evidently I needed to clean the yarn cache as noted in this comment. When I did, all in CPU land was fixed. |
|
@rosskevin's suggestion worked for me for the CPU issue. If you've installed yarn via npm instead of homebrew: |
|
I can confirm this was fixed for me in yarn 0.18 but was definitely an issue in yarn 0.17. |
|
Yeah, I recently started out using Yarn and I had no problem like above - I also tried to reproduce bug in 0.19.1 but it seems it's ok now. closing this. |
|
Is anyone still experiencing this issue? I think I might be but need to really check all the nitty gritty details before I report that I am. |
|
I saw this issue again, seems like doing:
helped. |
|
It seems like this issue is showing up again in Yarn 1.1.0 & workspaces. Consistently seeing problems on my Linux CI server building Gatsby sites. EDIT: I fixed things by adding |
|
I have this problem again with yarn 1.1.0 and now with 1.2.0 as well. I have a dependency that depends on a lot of babel packages. They are all installed except fro babel-loader. If I run yarn 0.27.5 babel-loader is installed, if I run yarn 1.2.0 only babel-loader is missing. yarn list babel-loader says its there and the lock file mentions it the same way it does babel-cli for example. Yet loader is inside my-framework/node_modules whereas all other my-framework deps are outside in the root. 0.27.5: 1.2.0 |
|
I narrowed down the babel-loader issue to this PR. #4086 reverting the merge into master makes yarn behave like 0.27.5. I will investigate further what exactly is the bug. Somehow babel-loader is not being hoisted while other similar deps are. You can reproduce this issue by adding react-scripts to a project, then run yarn to install. With 0.27.5 all react-scripts deps are hoisted including babel-loader, with yarn > 1.0 all are hoister except for babel-loader. Pinpointed the offending code in line 332-344 in package-hoister.js, with the comment: @arcanis @BYK What was the bug that #4086 was trying to fix? how do I reproduce it? I have a fix but I don't know if it regresses the original problem. Nevermind found repro steps: #3933. I can verify that with my fix the babel-loader issue is fixed and the repro steps on #3933 are still resolved as well. But it doesn't pass the unit test |
and others
Do you want to request a feature or report a bug?
bug
What is the current behavior?
after install, I am seeing errors 'chokidar' is not installed. It seems to be included in
babel-cli,watchpack, etc modules but it is not innode_modules. However, I canchokidarinyarn.lock. This makes me enable to dowebpack --watchIf the current behavior is a bug, please provide the steps to reproduce.
{ "name": "yarnjs-bug-missing-deps", "description": "", "version": "1.0.0", "author": "Jaeho Lee <[email protected]>", "licenses": "proprietary", "scripts": { "postinstall": "" }, "devDependencies": { "babel-cli": "^6.16.0", "babel-core": "^6.4.5", "webpack": "^1.12.12" } }Use this package.json to
yarnand seechokidaris missing in node_modulesWhat is the expected behavior?
chokidarshouldn't be missing; There could be another dependencies gone missing but currentlychokidaris only thing I can find so far.Please mention your node.js, yarn and operating system version.
Node v6.3.0, OSX 10.10.5
The text was updated successfully, but these errors were encountered: