just
just copied to clipboard
npm @just organization
Since orgs are free now with unlimited packages, you might consider grouping all packages under the @just/
organization while its available. This would help people find your other packages and help with name conflicts. I would be willing to help with this if wanted.
Thanks for the offer @brandonryan . How does backwards compatibility work here? Will links and imports redirect?
Basically, you would publish to the new packages and then deprecate the old ones. Also putting a message in the readme linking to the new package. People who install the old one will get a deprecation message via the npm cli https://docs.npmjs.com/cli/v8/commands/npm-deprecate
Decided against this