No such thing as `npm dedupe --production` ? about caxa HOT 3 CLOSED

Note: I only tested it with npm v6 (6.14.12), not npm v7.

from caxa.

Thanks for reaching out!

Hmmm, so it seems that npm dedupe --production only works in more recent versions of npm. What this command does is remove duplications and remove development dependencies. All in one command—cool stuff.

The caxa v1 way was incorrect, anyway: running npm dedupe would undo the work of npm prune --production, reinstalling the development dependencies. At least that’s what happens npm 7.10.0.

Here’s what you can do in your version of npm:

1. Use --no-dedupe to prevent caxa from running npm dedupe --production.
2. Use --prepare-command to run whatever commands you want from within the build directory before it’s packaged. You may use something like --prepare-command 'npm prune --production', for example.

Moving forward I think that people will be updating to more recent versions of npm and until they do this workaround seems pretty usable, so I think caxa will remain as it is and I’m closing the issue. If you disagree, please let me know! 😀

I’m looking forward to having balena CLI using caxa, please let me know how it goes and if there’s anything I can do on my side to help y’all out.

from caxa.

which I suspect may have been an accident / mistake -- was it?

No, it wasn’t 😀 https://youtu.be/XeTPAxYsT5w

from caxa.