A special thanks to all those who have clocked in some dev time on this project, we really appreciate your hard work. This is common in visual studio for instance. I can confirm the issue persist with 0. Reply to this email directly, view it on GitHub , or mute the thread. See for more details on Sass types.
It is recommended that you use includePaths in conjunction with this so that can find files when using the import directive. If any tests fail it will build from source. Is the yo generator trying to fetch somewhat outdated sass-node? I open a discussion with the plugin authors to discuss what it is you're trying to do. They may take zero or more input parameters and must return a value either synchronously return. Correct atom shell is not supported. I installed the node-sass 3. This issue as been explained many times in the issue tracker.
Switch node back to version 6 using nvm. I'm using it via the sass-loader in Webpack 2. There is likely additional logging output above. From now on, remember to stray away from using sudo when installing Node, npm, or even modifying npm packages. This is the only npm module that asks to be rebuilt. For my case, I was using both Meteor requires Node 0.
To avoid this overhead, you can use the package to call asynchronous importers from the synchronous code path. I searched a little on google but didn't find a fix yet. For those of us working on Unix-based systems, it's not uncommon to come across error messages complaining about your user permissions whenever installing new npm packages, especially when installing them globally. I reverted to previous released version yarn 0. To build the correct binary after changing your environment run npm rebuild node-sass It's also seems like you're running a very old version of node-sass. That means we have to specify sudo before every global install, which is annoying. Failed at the node-sass 4.
Still running npm rebuild node-sass all the time. I suspect there might be some sort of concurrency issue with the download of binaries in that specific folder. Make sure you have the latest version of node. A custom importer allows extension of the engine in both a synchronous and asynchronous manner. Here's what it's trying to tell me. When using data, it is recommended that you use this.
Node 5 47 is your local version, however atom has it's own embedded Node 0. While using this site, you agree to have read and accepted our ,. For one, the user that does this will inherently have no permissions to modify global npm packages when this happens; because we installed Node with sudo, the directory for global npm packages forever functions as though the root user has permissions, but nobody else. Unfortunately, for some reason, the current version of node-sass does not properly run its install script to download the binary file it needs to operate. I had the same problem and npm rebuild node-sass didn't entirely fix it. Output will be sent to stdout if the --output flag is omitted. Can't explain why the install file doesn't always get ran on each build.
It also accepts path to. In this case, running npm install again doesn't fix the issue because npm thinks it is installed. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Reinstalling Node I'm working under the assumption that we're using Ubuntu or a Debian-based Linux distro. Have a question about this project? Environment variables If you want to prepend Sass code before the actual entry file, you can set the data option. .
Make sure you have the latest version of node. Make sure you have the latest version of node. Hey, i have the same problem. The return value must be of one of these types as well. It does not occur in all projects where I use node-sass, and it does not occur consistently on every install. This usually happens because your environment has changed since running npm install. I found that for some reason no matter what I did even after the permissions issue was resolved, it still wouldn't always run the install.