PowerShell build-bits.ps1: Issue/error when building SPA JS dependencies before dotnet bits about eshoponcontainers HOT 5 CLOSED

Hi @CESARDELATORRE
This is an issue about your configuration.
You need to be sure that VS2017 is using the same nodejs that you are using from command line.
Go to "Tools -> Options -> Project and Solutions -> Web Package Management -> External Web Tools" and ensure that the nodejs you use from command line is listed before that the entry "$(VSINSTALLDIR)\Web\External"

This should solve the issue.

Please, keep in mind that the version bundled with VS2017 (5.x) is far more modern than the obsolete version shipped with VS2015, so maybe you are using the bundled version of VS without errors. But, then, as the architecture is not the same (VS is still a 32 bit process) all binary modules will not work when you use the command line (this is a limitation of node, only one architecture of the binary modules can be kept at same time). So, when you use node from command line, as your architecture is different (x64) the error is triggered.

Please, review and close the issue if solved :)

from eshoponcontainers.

Eduard, this is how I have it configured.

Do you mean the line ".\node_modules.bin" which is already listed before the entry "$(VSINSTALLDIR)\Web\External", or do you mean that I need to add a new entry like the following

?

from eshoponcontainers.

Hi!
Yes, you need to add a new entry like the second picture, but in 2nd position.
The ideal is the 1st one to be:
.\node_modules\bin
And the 2nd entry
c:\program files\nodejs (or whatever path you have nodejs installed)

Then the rest of entries. That order ensures two things:

1. Local node modules user over global ones (i. e. local gulp/bower used instead of global one) which is a preferred
2. Forcing VS to use the same nodejs as used in the CLI.

This should solve your issues.

Thx!

from eshoponcontainers.

This issue was mainly solved by running npm rebuild node-sass after running npm install within the SPA folder by using the command line.
Closing the issue.

from eshoponcontainers.

not helping if we are building everything from cli-windows/start-windows-containers.ps1

from eshoponcontainers.