-
Notifications
You must be signed in to change notification settings - Fork 43
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 i
fails
#12
Comments
@vith thanks for detailed report, I have checked on clean ubuntu installation with zero global deps and install working fine, it seems like a problem with plugin typescript transpiler. Other that that, I'm not sure what could be the problem. |
but event then solution should be working fine but without dev-bundle optimization, please try to run |
Same error after deleting I'll see if I can reproduce it in a new VM. |
@vith Would be great if you can share your findings :) Also please check maybe you have a typescript or jspm packages installed Pozdrawiam, 2016-08-12 15:23 GMT+02:00 Jason Papakostas notifications@github.com:
|
I am able to reproduce it in $ sudo pacman -S git nodejs npm
$ git clone https://github.com/piotrwitek/react-ts-jspm-starter-kit
$ cd react-ts-jspm-starter-kit
$ npm i Again no difference if I remove the Inside the VM there's definitely no global install of |
Thanks, I gonna check it also with antergos to see if that's some machine specific issue. |
I also just tested on I'm guessing the Ubuntu version you tested has old enough nodejs to not be affected. Arch Linux: node v6.3.1: affected |
this is my config, should be same as your original |
also working fine on my windows laptop with this config: (linux is a desktop machine)
|
Could you please also check for which architecture was the node binary used On Aug 12, 2016 4:23 PM, "Jason Papakostas" notifications@github.com
|
From my real Arch Linux environment: ~/react-ts-jspm-starter-kit master
❯ npm version
{ 'react-ts-jspm-starter-kit': '0.7.1',
npm: '3.10.6',
ares: '1.10.1-DEV',
http_parser: '2.7.1',
icu: '57.1',
modules: '48',
node: '6.3.1',
openssl: '1.0.2h',
uv: '1.9.1',
v8: '5.0.71.57',
zlib: '1.2.8' }
~/react-ts-jspm-starter-kit master
❯ file "$(which node)"
/usr/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=abc111a6272f59ebb7d3bb82a9514cb2b5341772, stripped I am unable to reproduce in a new Ubuntu 16.04.1 VM, but its nodejs is 4.2.6. Have you installed 6.3.1 from a PPA? If so which one? |
I don't get the error either on Ubuntu with nodejs from https://deb.nodesource.com/setup_6.x: $ npm version
{ 'react-ts-jspm-starter-kit': '0.7.1',
npm: '3.10.3',
ares: '1.10.1-DEV',
http_parser: '2.7.0',
icu: '56.1',
modules: '48',
node: '6.3.1',
openssl: '1.0.2h',
uv: '1.9.1',
v8: '5.0.71.57',
zlib: '1.2.8' } |
Yes I have installed from nodesource, seems like Arch linux using some kind of community driven repository and might be the case of some differences in node binary |
Arch Linux's "community" repo contains official packages. It's just called community because packages in there started out as unofficial AUR (Arch User Repository) packages but have been adopted by the official maintainers (Trusted Users). From Fedora using https://rpm.nodesource.com/setup_6.x, where I do get the error: [vith@localhost react-ts-jspm-starter-kit]$ npm version
{ 'react-ts-jspm-starter-kit': '0.7.1',
npm: '3.10.3',
ares: '1.10.1-DEV',
http_parser: '2.7.0',
icu: '56.1',
modules: '48',
node: '6.3.1',
openssl: '1.0.2h',
uv: '1.9.1',
v8: '5.0.71.57',
zlib: '1.2.8' }
[vith@localhost react-ts-jspm-starter-kit]$ file `which node`
/usr/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=0551551ef484b7875da457847daf6f01060c9269, stripped
|
Yea seems like a random bug in node or plugin-typescript. |
I'm closing this as I cannot see anything possible that I could do |
full terminal session
version:
v0.7.1-1-gae651fc
The text was updated successfully, but these errors were encountered: