`cross-env` & `patch-package`

[kidonng]

Not sure about these as they are mostly development only dependencies, but worth mentioning due to their still considerable downloads.

cross-env

• Yarn: built-in support
• pnpm: built-in support (after setting shellEmulator: true)
• npm & deno & bun: unknown

patch-package

Some alternatives are listed in its readme but probably worth repeating here.

• Yarn: built-in support
• pnpm: built-in support
• npm & deno & bun: unknown

[43081j]

if we can find a way to natively do cross-env in node, that'd be huge

afaik there isn't one yet though

[kidonng]

There's --env-file. A somewhat cumbersome alternative could be:

"scripts": {
	"cross-env": "cross-env FOO=BAR npm run dev",
	"env-file": "node --env-file env/foo.env -e \"child_process.spawn('npm', ['run', 'dev'], { stdio: 'inherit' })\""
}

# foo.env
FOO=BAR

Though child_process is its own can of worms.

[JounQin]

patch-package has better experience than yarn built-in support and npm doesn't support patch at all. I'm still trying to concat @ds300 and @orta to continue the work ds300/patch-package#507 and I've published it as @unts/patch-package as a temporary solution. I haven't decided to release @unts/patch-package as patch-package-x yet, may do it in the future.

Anyone helps to contact the original authors @ds300 and @orta would be appreciated.

[43081j]

Last time I talked to orta about this, his opinion seemed to be that package managers should handle this. So I would suggest we maintain a package until npm can do it itself.

I think it is generally agreed that the original patch-package is happy to be replaced

[JounQin]

So I would suggest we maintain a package until npm can do it itself.

If we can continue to use the patch-package brand that's would greater and appreciate before npm lands support for that.

I think it is generally agreed that the original patch-package is happy to be replaced

Sure, I've already raised yarnpkg/berry#6772 but haven't received any responses yet.

For most users, patch-package still has better DX than yarn's current built-in.

[43081j]

It doesn't seem likely we will be able to change patch-package. Meanwhile, we could start trialling out your fork. We should battle test it more before moving everyone to it, though. A start would be to collab with some projects that are open to helping try it out

[JounQin]

It doesn't seem likely we will be able to change patch-package.

Yeah, that's the most unfortunate part, I may start the true fork progress soon later.

[benmccann]

We're switching from cross-env to pnpm's shellEmulator here: sveltejs/kit#14141. Sharing as some of the things discovered would be nice to mention in the write up. It helped us simplify some other things worth mentioning as benefits (e.g. we can do rm -rf now as opposed to a long node -e incantation or extra dependencies from rimraf/premove)

[lishaduck]

Bun runs scripts via their $ function, so I'd assume it replaces cross-env.

It helped us simplify some other things worth mentioning as benefits (e.g. we can do rm -rf now as opposed to a long node -e incantation or extra dependencies from rimraf/premove)

To clarify for the non-Svelters, shellEmulator is awesome, but unfortunately doesn't handle rm -rf (as Svelte seems to have found out 😉), so we still need premove.
Kinda wonder how bad it'd be to create a very, very tiny, no-lib/pure-cli rmrf implementation. Probably not worth it, but still... it shouldn't be that hard... right?

[gameroman]

cross-env

#	Downloads/month	Traffic	Version	Package
1	3.52M	27.06 GB	^7.0.3	@react-three/drei
2	2.97M	22.81 GB	^7.0.3	firebase-tools
3	2.01M	15.50 GB	^10.0.0	argon2
4	491.73k	3.78 GB	^7.0.3	@strapi/admin
5	329.52k	2.53 GB	7.0.3	@excalidraw/excalidraw
6	213.40k	1.64 GB	^7.0.3	strapi-admin
7	202.43k	1.56 GB	^7.0.3	react-images
8	118.45k	911.14 MB	^3.1.4	nps-utils
9	104.39k	803.00 MB	^5.2.1	@medusajs/medusa-js
10	78.65k	604.99 MB	^7.0.3	yup-phone

patch-package

#	Downloads/month	Traffic	Version	Package
1	799.73k	93.71 GB	^6.5.1	cy2
2	92.09k	10.79 GB	^8.0.0	secretjs
3	79.67k	9.33 GB	8.0.0	@gluestack-ui/nativewind-utils

[gameroman]

@43081j should I open an ecosystem issue for this instead?

[43081j]

since its unclear what the alternatives are, we can't really add mappings.

so sure lets move this to the ecosystem issues repo and link back to this issue for context. remember it is about patch-package and cross-env