Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Use latest npm in AppVeyor #996

Closed
xzyfer opened this issue Jun 10, 2015 · 8 comments
Closed

Use latest npm in AppVeyor #996

xzyfer opened this issue Jun 10, 2015 · 8 comments
Assignees
@xzyfer
Labels
Bug - Confirmed External - NPM
Milestone
v3.3.0

Comments

@xzyfer
Copy link
Contributor

xzyfer commented Jun 10, 2015

For 3.2.0 we had to lock to npm@2.7.5 (#995) to work around an npm regression with Windows (npm/npm#8517).

Once this is resolved we should revert #995.
@xzyfer xzyfer self-assigned this Jun 10, 2015
@saper
Copy link
Member

saper commented Jul 2, 2015

We have a suggestion from @FeodorFitsner not to use PowerShell to invoke npm. Any thought on that @am11 (we did to fix AppVeyor in c64d596) ?

@am11
Copy link
Contributor

am11 commented Jul 2, 2015

@saper, you are right. I think we need to change:

- ps: npm install --msvs_version=2013

to:

- npm install --msvs_version=2013

#844 (comment)

saper added a commit to saper/node-sass that referenced this issue Jul 6, 2015
@saper
Don't launch npm in the PowerShell
f95af46 
There might be issues with running npm under PS,
therefore let's run npm under CMD.

sass#996

http://help.appveyor.com/discussions/problems/2347-npm-275prefer-global-warning-causes-failure-command-executed-with-exception#comment_37223989

npm/npm#8517

Effectively reverts: sass#995
@saper saper mentioned this issue Jul 6, 2015
Merged
@saper
Copy link
Member

saper commented Jul 6, 2015

Thanks @am11, looks like #1024 fixes that problem indeed.

@saper
Copy link
Member

saper commented Jul 7, 2015

A hopefully proper fix for npm: npm/npm#8841

@xzyfer
Copy link
Contributor Author

xzyfer commented Jul 13, 2015

@saper if you feel this is fixed by #1024 feel free to close this issue.

@xzyfer xzyfer added this to the next.patch milestone Jul 13, 2015
@xzyfer
Copy link
Contributor Author

xzyfer commented Aug 8, 2015

Fixed by 1024

@xzyfer xzyfer closed this as completed Aug 8, 2015
@saper
Copy link
Member

saper commented Aug 8, 2015

Will be fixed in npm soon, hopefully :)

@xzyfer xzyfer modified the milestones: next.patch, v3.3.0 Aug 26, 2015
@xzyfer
Copy link
Contributor Author

xzyfer commented Aug 28, 2015

This has been fixed upstream in npm 🎉

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@xzyfer xzyfer

Labels
Bug - Confirmed External - NPM
Projects
None yet
Milestone
v3.3.0
Development

No branches or pull requests
3 participants
@saper @xzyfer @am11