Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use npmlog for all install script output #1796

Merged
merged 2 commits into from
Nov 13, 2016
Merged

Conversation

xzyfer
Copy link
Contributor

@xzyfer xzyfer commented Nov 13, 2016

In for a penny in for a pound. I also noticed that #1786 resulted
in some funky looking console output. I've taken this opportunity to
tidy up our install script output whilst maintaining the information
useful for debugging install issues.

> node-sass@3.11.3 install /Users/xzyfer/Projects/Sass/upstream/node-sass
> node scripts/install.js

http node-sass install Downloading binary from https://github.com/sass/node-sass/releases/download/v3.11.3/darwin-x64-47_binding.node
http node-sass install Download complete
info node-sass install Binary saved at /Users/xzyfer/Projects/Sass/upstream/node-sass/vendor/darwin-x64-47/binding.node

> node-sass@3.11.3 postinstall /Users/xzyfer/Projects/Sass/upstream/node-sass
> node scripts/build.js

info node-sass build Binary found at /Users/xzyfer/Projects/Sass/upstream/node-sass/vendor/darwin-x64-47/binding.node
info node-sass build Testing binary
info node-sass build Binary is fine

> node-sass@3.11.3 prepublish /Users/xzyfer/Projects/Sass/upstream/node-sass
> not-in-install && node scripts/prepublish.js || in-install

@xzyfer xzyfer force-pushed the feat/clean-up-script-logging branch from 62246dd to ed885bc Compare November 13, 2016 07:22
In for a penny in for a pound. I also  noticed that #1786 resulted
in some funky looking console output. I've taken this opportunity to
tidy up our install script output whilst maintaining the information
useful for debugging install issues.

```
> node-sass@3.11.3 install /Users/xzyfer/Projects/Sass/upstream/node-sass
> node scripts/install.js

http node-sass install Downloading binary from https://github.com/sass/node-sass/releases/download/v3.11.3/darwin-x64-47_binding.node
http node-sass install Download complete
info node-sass install Binary saved at /Users/xzyfer/Projects/Sass/upstream/node-sass/vendor/darwin-x64-47/binding.node

> node-sass@3.11.3 postinstall /Users/xzyfer/Projects/Sass/upstream/node-sass
> node scripts/build.js

info node-sass build Binary found at /Users/xzyfer/Projects/Sass/upstream/node-sass/vendor/darwin-x64-47/binding.node
info node-sass build Testing binary
info node-sass build Binary is fine

> node-sass@3.11.3 prepublish /Users/xzyfer/Projects/Sass/upstream/node-sass
> not-in-install && node scripts/prepublish.js || in-install
```
@xzyfer xzyfer force-pushed the feat/clean-up-script-logging branch from ed885bc to 0f2e004 Compare November 13, 2016 10:59
@xzyfer xzyfer merged commit e54581d into master Nov 13, 2016
@xzyfer xzyfer deleted the feat/clean-up-script-logging branch November 13, 2016 11:31
xzyfer added a commit that referenced this pull request Nov 15, 2016
We started using npmlog for install logging in #1786, then went all
out in #1796. npmlog has caused some issues, namely #1805. It doesn't
provided enough value for how troublesome it is.

The problem sparked #1786 was resolved in 5c7fb7f.
xzyfer added a commit that referenced this pull request Nov 15, 2016
We started using npmlog for install logging in #1786, then went all
out in #1796. npmlog has caused some issues, namely #1805. It doesn't
provided enough value for how troublesome it is.

The problem sparked #1786 was resolved in 5c7fb7f.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant