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

npm ERR! invalid: @emmetio/css-parser@0.4.0 /home/markus/tmp/vscode/extensions/emmet/node_modules/@emmetio/css-parser #32941

Closed
octoploid opened this issue Aug 22, 2017 · 7 comments
Assignees
Labels
emmet Emmet related issues

Comments

@octoploid
Copy link

On Linux vscode fails to build:

 % ./scripts/npm.sh install --arch=x64 && gulp vscode-linux-x64 
...
[11:38:43] Finished 'optimize-vscode' after 29 s                                         
[11:38:43] Starting 'vscode-linux-x64'...   
Unhandled Rejection at: Promise Promise {   
  <rejected> { Error: Command failed: npm list --production --parseable --depth=99999    
npm ERR! invalid: @emmetio/css-parser@0.4.0 /home/markus/tmp/vscode/extensions/emmet/node_modules/@emmetio/css-parser                                                              

    at ChildProcess.exithandler (child_process.js:270:12)                                
    at emitTwo (events.js:125:13)           
    at ChildProcess.emit (events.js:213:7)  
    at maybeClose (internal/child_process.js:927:16)                                     
    at Socket.stream.socket.on (internal/child_process.js:348:11)                        
    at emitOne (events.js:115:13)           
    at Socket.emit (events.js:210:7)        
    at Pipe._handle.close [as _onclose] (net.js:545:12)                                  
  killed: false,                            
  code: 1,                                  
  signal: null,                             
  cmd: 'npm list --production --parseable --depth=99999' } } reason: { Error: Command failed: npm list --production --parseable --depth=99999                                      
npm ERR! invalid: @emmetio/css-parser@0.4.0 /home/markus/tmp/vscode/extensions/emmet/node_modules/@emmetio/css-parser                                                              

    at ChildProcess.exithandler (child_process.js:270:12)                                
    at emitTwo (events.js:125:13)           
    at ChildProcess.emit (events.js:213:7)  
    at maybeClose (internal/child_process.js:927:16)                                     
    at Socket.stream.socket.on (internal/child_process.js:348:11)                        
    at emitOne (events.js:115:13)           
    at Socket.emit (events.js:210:7)        
    at Pipe._handle.close [as _onclose] (net.js:545:12)                                  
  killed: false,                            
  code: 1,                                  
  signal: null,                             
  cmd: 'npm list --production --parseable --depth=99999' } 


 % gulp --version
[11:47:51] CLI version 3.9.1
[11:47:51] Local version 3.9.1
 % npm --version
3.10.8

@Tyriar Tyriar added the emmet Emmet related issues label Aug 22, 2017
@ramya-rao-a
Copy link
Contributor

Can you do a git clean -xfd and try again?

@octoploid
Copy link
Author

Oh, I already did. It doesn't help.

@ramya-rao-a
Copy link
Contributor

@Tyriar had another idea of using gulp vscode-linux-x64 --max_old_space_size=4096 to ensure node has enough memory

If the issue is still isn't fixed, I'll try on an linux machine tomorrow.

@octoploid
Copy link
Author

Unfortunately --max_old_space_size=4096 doesn't help.

@Tyriar
Copy link
Member

Tyriar commented Aug 23, 2017

I can't seem to reproduce and our build machines seem fine as well. I'm running npm@3.10.10, perhaps that's the issue? Could you try running npm i -g npm@3.10.10 and seeing if that fixes it?

You could also try installing that particular module in a new folder and see if you run into a problem:

mkdir tmp
cd tmp
npm init -y
npm i -S git://github.com/ramya-rao-a/css-parser.git#370c480ac103bd17c7bcfb34bf5d577dc40d3660
npm list

@octoploid
Copy link
Author

@Tyriar Updating to npm@3.10.10 does fix the issue. Thanks.
Maybe you should mention it in your documentation?

@ramya-rao-a
Copy link
Contributor

cc @joaomoreno About need for npm@3.10.10 and adding it to documentation

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
emmet Emmet related issues
Projects
None yet
Development

No branches or pull requests

3 participants