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

Can't Initialize a project with 1.7.0 image #19

Open
PiWiBardy opened this Issue Nov 13, 2018 · 8 comments

Comments

Projects
None yet
5 participants
@PiWiBardy
Copy link

PiWiBardy commented Nov 13, 2018

Hi,

I'm facing an error while initializing a project with yeoman in the 1.7.0 image.

i'm getting the following error

====================================================

node-sass@4.9.3 install /usr/app/spfx/node_modules/node-sass
node scripts/install.js

fs.js:646
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^

Error: EINVAL: invalid argument, open '/usr/app/spfx/node_modules/node-sass/package.json'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.Module._extensions..json (module.js:670:20)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/usr/app/spfx/node_modules/node-sass/lib/extensions.js:7:9)
at Module._compile (module.js:653:30)

=========================================================

i tried with the 1.6 and the 1.5.1 image and it works fine.

thanks to find below the choice done during the yo man wizard

https://pbs.twimg.com/media/DrvDtx4WsAAZadq.jpg

Regards,

@Concisive

This comment has been minimized.

Copy link

Concisive commented Nov 13, 2018

I have just encountered the same issue on Docker for Windows. I created my own image based on the latest 1.7.0 dockerfile but I downgraded the version of node to 8.9.4. The first line of my dockerfile reads:

FROM node:8.9.4

The rest of the file is the same.

This change appears to work but I have not had time to test it extensively.

@PiWiBardy

This comment has been minimized.

Copy link
Author

PiWiBardy commented Nov 13, 2018

I tried to rebuild it with the node 8.11.3 ( as it was the version used for the 1.6.0 image ) and it's working fine.. i'm doing further test..

@PiWiBardy

This comment has been minimized.

Copy link
Author

PiWiBardy commented Nov 15, 2018

it's maybe related to this issue : sass/node-sass#2520

@waldekmastykarz

This comment has been minimized.

Copy link
Owner

waldekmastykarz commented Nov 15, 2018

Thanks for looking into it. Let's see if the suggestion from the issue you mentioned would help to fix the issue on Windows

@JonasBjerke89

This comment has been minimized.

Copy link

JonasBjerke89 commented Dec 13, 2018

Any news on this matter?

@waldekmastykarz

This comment has been minimized.

Copy link
Owner

waldekmastykarz commented Dec 13, 2018

Unfortunately, not yet. Thanks for checking in though. I've been busy with other things lately and didn't have the time to look into this yet.

@YannickRe

This comment has been minimized.

Copy link

YannickRe commented Dec 21, 2018

Same issue here, it worked using yarn instead of npm.

@waldekmastykarz

This comment has been minimized.

Copy link
Owner

waldekmastykarz commented Jan 13, 2019

As @YannickRe mentioned, installing packages works using yarn (yo @microsoft/sharepoint --package-manager yarn). When trying to use npm, I'm getting the reported error and when I try to mount node_modules as a volume, I'm getting checksum errors on typescript and other packages. So seems like using package managers other than npm is the way to go, at least now.

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