[0.17.0] Issues with node-sass #1832
Comments
|
Can't reproduce this with latest master: |
|
@hassankhan, can you checkout master and try on it? |
|
I can confirm this is happening with our CI build with yarn 17. It works when I clear the cache but like @hassankhan mentioned it happens on the second run. Node v6.1.0 |
|
I just tried with the latest master, and while I do see Node 7.1.0 |
|
This is now resolved for me with Yarn 0.17.2. |
|
Closing this. Please feel free to let us know if you face this problem in |
|
I'm sorry, I spoke too soon. I thought I tested this with my |
|
@jswanner no worries. Thanks for reporting it back though 😄 |
|
Sorry, late to the party, but yeah same thing, no dice 😢 |
|
FYI on my project (which has a lot of dependencies, but I think this is the problem). I can see that Yarn (0.17.2) removes some dependencies after a run. Notice the lines stating After the Then, if I run But then So, the dependencies being unbuilt in the final step are as far as I can see not being removed by npm prune. Somehow |
|
So I am trying to repro on master branch: Everything seems in place. I think binding.node is downloaded instead of being rebuilt. Anyway, we need a step by step guide to repro this |
|
@bestander it wasn't working me for either. The build step wasn't happening. After a |
This seems to be very difficult to reproduce consistently. 😕 It easily brings up red herrings, since it's likely that something you try at first seemingly fixes it, and then it only resurfaces later. @STRML has some ongoing work in #1852 (comment) / https://github.com/STRML/yarn-install-lifecycle-bug if someone else manages to get a reliable repro case. As far as I can see, this looks like the same root issue as #1848, #1852 and #1872, right? Or has there been some indication that there are two separate things going on?
OS X 10.11.6 here. |
|
These all seem related. For those of you currently experiencing it, could you please make copies of your local and homedir In my case, removing and recreating my |
|
So just updated to Yarn 0.17.4 and running |
|
Yes they all seem related. |
|
@hassankhan, if you run |
|
I had the same problem, removing I also noticed some segmentation fault while running yarn on projects with a lot of dependencies and the cache was empty, and after it happened, node-sass had been put in the node_modules folder, but vendor wasn't there. So I suspect that the segmentation fault happens when the post install scripts are run. Something like that... but I can't find the error log anymore with yarn 0.17.3.... |
|
@wyze Nope, did what you said but I can't reproduce the error any more. Seems to be working fine now 👍 |
|
#1912 is important to fix - Yarn silences build errors and this leaves us with inconsistent state |
|
Is this still a thing with Had started seeing something along these lines with the bump to |
+ upgrade all deps + force yarn@0.16, see yarnpkg/yarn#1832 fixes #1577
+ upgrade all deps + force yarn@0.16, see yarnpkg/yarn#1832 fixes #1577
+ upgrade all deps + force yarn@0.16, see yarnpkg/yarn#1832 fixes #1577
+ upgrade all deps + force yarn@0.16, see yarnpkg/yarn#1832 fixes #1577
+ upgrade all deps + force yarn@0.16, see yarnpkg/yarn#1832 fixes #1577
|
I think it was #1663 that fixed this. Closing as it is resolved. |
|
FYI It wasn't working for me right after upgrading yarn to v0.17.4, but this fixed it: |
|
Still getting reports of this in 0.17.6 - sass/node-sass#1804 (comment) |
|
karma-runner/karma-phantomjs-launcher#120 is related as well |
|
Same as @Danita. Was seeing it in 0.17.9, just doing |
|
Possibly related: #2104 |
|
Still happenening with yarn 0.19.1 :/ (Even after clearing the cache and deleting node_modules) |
|
0.20.0 fixed it for OSX, but still getting this on Linux with Codeship. The vendor folder just isn't there :( |
SCSS wasn't the issue... seems to be a yarn buiding issue on Heroku: sass/node-sass#1579 yarnpkg/yarn#1832
|
Still not fixed with 0.21.3 on macOS 10.12 :( |
😢 |
|
For those who still have this issue please open a new one with steps to reproduce and cc me |
|
FYI, I no longer see this issue with yarn 22 and now 23 on macOS. Including fresh install for new project. |
|
How to reproduce consistently: CircleCI 2.0 Docker program.
The first run, the docker container will be built, no cache will exist, yarn will run an install, and then perform a successful compilation of sass using gulp-sass. It will succeed. Do another noop checkin. The following build will use the cache saved from the previous successful run, restore the cache, and then run a ./.circleci/config.yml version: 2
jobs:
build:
working_directory: ~/project
docker:
- image: node:7.10
steps:
- checkout
- restore_cache:
key: deps-{{ .Branch }}-{{ checksum "yarn.lock" }}
- run:
command: yarn install --pure-lockfile --no-progress
- save_cache:
key: deps-{{ .Branch }}-{{ checksum "yarn.lock" }}
paths:
- node_modules
# ADD THIS COMMAND HERE THAT USES NODE-SASS / GULP-SASS
# - run:
# command: yarn run css Refs: |
|
Commenting on old closed issue won't help, please create a new one if you have repro steps with latest yarn |
and others
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
Have a package that uses
node-sassas a dependency, then runyarn install. Running it a second time will complete the install, butnode-sasswill not work.What is the expected behavior?
No errors, just fun.
Please mention your node.js, yarn and operating system version.
Node v4.6.0
Yarn v0.17.0
macOS 10.11.6
The text was updated successfully, but these errors were encountered: