| Name |
Last commit
|
Last update |
|---|---|---|
| bin | ||
| lib | ||
| media | ||
| scripts | ||
| src | ||
| test | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .jshintignore | ||
| .jshintrc | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| TROUBLESHOOTING.md | ||
| appveyor.yml | ||
| binding.gyp | ||
| package.json |
This is necessary because if a user is bundling node-sass in their package, the vendor directory should stay so that the user isn't required to run 'npm rebuild' afterwards, assuming that it was originally installed on a like-architecture. However, at the same time, when publishing, we don't want to include the binaries since they may not work for a user plus there's the build step that tries to download the correct binary for the current architecture. Unfortunately, npm's prepublish hook runs on both prepublish *and* npm install (see npm/npm#10074), so, using in-publish as a workaround to get the prepublish script to only run prepublish and pack but not on install. Fixes #1183 Closes #1384
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitmodules | Loading commit data... | |
| .jshintignore | Loading commit data... | |
| .jshintrc | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |