Are you aware of a one-liner that would npm install in a portable way across OSes?
I’ve also tested using
setup: ["deps.get", "cmd cd assets", "cmd npm install"]
I believe each command is running in subshell so the directory change doesn’t persist.
wojtekmach
Hex Core Team
thiagomajesk
I’m researching what are the options. I’ve tested
- All combinations of using the
--prefixflag - Specifing the location of package.json:
npm install --prefix ./assets ./assets.
This doesn’t work, see here: Run npm install in a different directory - Nerdy Mishka - Nerdy Mishka.
Interestingly enough, since the npm repository was moved to GitHub - npm/cli: the package manager for JavaScript · GitHub; there’s no trace of this problem being discussed, even though the old archived repository has open issues about that 
. I’m not sure wether this is a regression or if it was even fixed at some point.
0
Rainer
I’ve got a problem creating a release using Docker, maybe someone can help?
I’m using the Dockerfile from Deploying with Releases — Phoenix v1.8.8
Everything seems fine until it fails short time before finish with following message:
Step 23/26 : COPY --from=build --chown=nobody:nobody /app/_build/prod/rel/my_app ./
COPY failed: stat /var/lib/docker/overlay2/eb170e088a8c087d23f677f13e3f832062014759af8564efe30c4292656da00a/merged/app/_build/prod/rel/my_app: no such file or directory
0
NobbZ
You probably need to change the name of the file to match the name of your release in that line.
1
Rainer
Oh man, thx 
Of course, how could I’ve been so blind, that happens when doing things late at night
Working now 
/edit:
Works fine on Linux, however on Windows I run into the same issue as others here:
Step 14/26 : RUN npm run --prefix ./assets deploy
---> Running in 866f8ef90270
> @ deploy /app/assets
> webpack --mode production
/app/assets/node_modules/.bin/webpack: line 1: XSym: not found
/app/assets/node_modules/.bin/webpack: line 2: 0025: not found
/app/assets/node_modules/.bin/webpack: line 3: 04ec15c01fc3c268b6405aedcd29653e: not found
/app/assets/node_modules/.bin/webpack: line 4: ../webpack/bin/webpack.js: not found
0
josevalim
Creator of Elixir
npm run --prefix assets does not work on Windows. If you do something like cd assets && npm run deploy then it should be good to go.
1
Rainer
Thanks for the reply. I’ve tried this already as I’ve seen this suggestion somewhere else, but it does not seem to work for me, the result is the same.
However, it’s not critical for me as I’m working mainly with Linux, it’s just a bit sad 
Thanks for all your work 
0
thiagomajesk
The main problem I see is this being released in the default generators for Phoenix 1.5; despite signaling otherwise. Right now, following the README to setup a brand new project on Windows just fails and could lead someone in a trail to Stack Overflow questions and undocumented NPM behaviors (Also, as I said before, there’s no track of this issue in the new NPM repository).
Could someone say something about the reasoning behind that? Motivations, what changed, etc?
Also, is there anything that can be done to ease the experience with Phoenix 1.5 for Windows users?
0
chrismccord
Creator of Phoenix
To be clear, we have been tracking the node --prefix issues on windows for years, and my comment last June was before someone re-raised the issue later in the year, and all testing on windows confirmed it worked as expected. It seems that it’s still hit or miss in the wild ,but we merged assuming node finally solved the windows issues in this regard. Phoenix master/v1.5 has already reverted this change and will be the previous behavior in the next release 
2
thiagomajesk
Hey @chrismccord!
Thanks a lot for the confirmation 
..
I was suspecting this was a regression precisely because of said comment, but wasn’t sure because I couldn’t find any track of this issue being discussed. Thanks for all the effort!
Also, let me know if I can help with anything while I’m still required to use Windows for development.
Cheers!
0