Very long linking when doing 'yarn --production' (or how to get production clean yarn.lock quickly)

[wclr]

I'm using the following deploy strategy while building nodejs apps docker images:

• My app's manifest has dependencies and some devDependencies.
• I copy both package.json and yalc.lock files into new directorory.
• Run yarn --production (after this yarn.lock is change to reflect only production deps, and node_modules have only production deps)
• Then again I copy yalc.lock from dev project.
• Run yarn --production
• Linking dependencies.. takes very long.

I wonder if it is possible to make such scenario of more efficient? (This scenario is a part of preparing production files for docker image).

[wclr]

Well actually I could call this issue How to purge yalc.lock from dev devependencies quickly. Before placing package.json into docker container I purge it just removing devDependencies - I would like to have yarn.lock too production clean, so that if those files not changed on rebuild docker will take cached layer with installed deps. And If we leave yarn.lock as in dev version this strategy is influenced by dev stuff in it, which is not needed in production.

So executing yarn --production (or just yarn with the purged package.json) before placing files to container - is a way to get yarn.lock production clean. But it takes long as described in OP.

Probably yarn could do something like this without touching FS, just analyzing graph and removing dev related stuff, leaving production.

[wclr]

@bestander
Interesting to hear comment on this: is it possible to purge dev dependencies related stuff from yalc.lock without touching fs, quickly, in principle?

[wclr]

Any comment on this?

[bestander]

Sorry, @whitecolor, I was deeply involved in another project.

[bestander]

Interesting to hear comment on this: is it possible to purge dev dependencies related stuff from yalc.lock without touching fs, quickly, in principle?

I think it is possible.
yarn.lock holds the dependency tree and root package.json lisholdss top level dependencies.
If we assume that yarn.lock is consistent with package.json then we can pass through yarn.lock and remove all top level dev dependencies' entries and then all orphaned entries.

[bestander]

It's strange though that linking of yarn install --production takes longer with dev dependencies in yarn.lock file.
As I remember there may be still fetching done for --production installs but linking should only be done for the dependencies that are being installed.