Fail on node-sass post-install commands #786
Comments
|
Same here with |
|
I have the same error (Cannot find module 'stringstream') but when installing phantomjs.
|
|
same |
|
Looks like a duplicate issue from #987 |
|
@carneiror looks like you are right |
|
#987 was closed 9 days ago, but I'm still seeing this issue with node-sass and yarn 0.16.1. Here's the shell log from trying to install it in a new project. May I suggest we re-open? Or am I missing something? |
|
same here like @mike-hearn Haven't look into it carefully, just guess maybe because that script depends on that error came from function getCachePath() {
return process.env.npm_config_sass_binary_cache ||
process.env.npm_config_cache;
} |
|
@mike-hearn @whitetrefoil so should I reopen this issue to indicate that the problem still exists? |
|
Have the same issue and what most interesting part is that i didn't change anything in package.json of a project, but "yesterday" everything worked just fine and "today" i have this error: |
|
It seems that I tried to workaround it by adding |
|
same @mike-hearn
yarn add v0.16.1 TypeError: Path must be a string. Received undefined |
|
The same problem |
|
Downgrading to [email protected] works for me today. |
|
Same problem here. Downgrade helped |
|
@dopesong can you try |
|
Can you retest with |
|
Still an issue with Yarn |
|
I was getting the same with yarn |
|
Getting this issue on Ubuntu 14.04 w/ node 7.7.3 (and various older 7.x nodes) but only with a locally-installed copy of yarn (i.e., npm install yarn). If I run a globally-installed copy instead, it works correctly. Trouble is, the machines at work have old (and unchangeable) copies of Node so I have to run a fetch-nvm-and-node script before running yarn, and I don't want the builds to require human interaction to enter a sudo password to globally install yarn. Here's my own output: |
|
I'm able to get around this by having |
|
I'm having issues with this where a dependency has a postinstall script that requires node-sass. Adding |
|
@AlejandroHuerta, can you share the steps to reproduce your issue? |
|
I've got another insight on this one: |
|
@bestander here is a simple repro: then npm rebuild node-sass will fail. This problem does not happen when installing the packages with npm. |
|
This seems to be fixed with Yarn 1.0+. Can someone confirm? @bherila I wasn't able to reproduce the issue with the steps you provided on latest master. If Yarn 1.0.2 still doesn't work for you, would you mind trying one of the nightlies from https://yarnpkg.com/en/docs/nightly |
|
Yarn 1.0.2 didn't work for me, but the current nightly build (1.0.2-20170922.1215) solved this issue for me. |
|
|
* To be able to run a devcontainer its own network (not just --net host), webpack-dev-server serves on 0.0.0.0. * Fix expired signature (EXPKEYSIG): yarnpkg/yarn#786
* To be able to run a devcontainer its own network (not just --net host), webpack-dev-server serves on 0.0.0.0. * Fix expired signature (EXPKEYSIG): yarnpkg/yarn#786
* To be able to run a devcontainer its own network (not just --net host), webpack-dev-server serves on 0.0.0.0. * Fix expired signature (EXPKEYSIG): yarnpkg/yarn#786
and others
Do you want to request a feature or report a bug?
A bug.
What is the current behavior?
Yarn cannot install
node-sasspackage.Log
If the current behavior is a bug, please provide the steps to reproduce.
package.jsonon working project withnode-sass(I tried with my Identity build system)node_modulesif existsyarnfrom shellWhat is the expected behavior?
All packages is installed and
gulpbuild is working.Please mention your node.js, yarn and operating system version.
macOS Sierra Beta 10.12.1 (16B2338c)
The text was updated successfully, but these errors were encountered: