Continue publishing preact/compat as standalone node module also?

I’d like to suggest you continue publishing the npm package preact-compat as alternative method of installing/using preact/compat.

This would make it possible to use npm and yarn’s native package.json dependency renaming syntax and skip installing 3rd party aliasing-plugins and/or relying on bundler config tricks.

Like so…

npm install react@npm:preact-compat@^10 react-dom@npm:preact-compat@^10

resulting in these depdendency lines in package.json

	"react": "npm:preact-compat@^10",
	"react-dom": "npm:preact-compat@^10",

The only thing that might make this unfeasible, is if this would result in large amounts of code being imported twice - once from node_modules/react and then again from node_modules/react-dom. I’m not familiar enough with the preact codebase to judge how tight the coupling is between the "react"y and "react-dom"y bits of Preact.

[andrewiggins]

Does npm aliases work for compat? At least when they were first introduced, it only aliased the package for yourself, not for any libraries you add (e.g. when your code imported react you would get preact-compat but if you used react-router, it’s react import would still be react, not compat). That’s my understanding of the relevant section in the RFC (see the paragraph about problems this RFC does not address). Has npm changed the behavior of aliases since this RFC was released?

[caub]

@marvinhagemeister Thanks, I did notice that, no worry. I’m just posting my solution for the record, and comparing with what others are doing