`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.