Package name migration

[jamesrweb]

In the next major release of this library (v5.0.0) the dependency name will change from react-p5-wrapper to @p5-wrapper/react and the react-p5-wrapper name will be deprecated.

We have already deployed our NextJS dynamic component under the @p5-wrapper/next package name and this package will be the second to be deployed using this new namespace convention.

Version 5.0.0 will be released on the 1st of May 2023, at which point the old name will be deprecated, although still usable for version 4.x.x and below, and the new one in place for version 5.x.x and above.

For reference and clarity, the changes for version 5.0.0 will largely be represented by the changes in pull request #240. That pull request contains largely internal changes to move us from Webpack + Rollup + Jest to pure Vite and Vitest. In terms of API changes, nothing will change how you use the component as it currently stands.

I will keep this thread updated when the changes are deployed and of course if there are any open questions or topics of concern, please do let me know in the discussion thread below.

[jamesrweb]

The @p5-wrapper/react version is available already on NPM for those wishing to migrate in advance. It is still on version 4.1.2 so all you would have to do it replace the name in your package.json and you should be good to go. The only difference between the react-p5-wrapper and @p5-wrapper/react versions is that the former is bundled with Rollup and the latter with the new vite setup.

The bundle size is reduced purely by swapping the build tool but only by a very slim margin:

Package	Bundler	Bundle Size	Bundle Size (gzip)	Difference
@p5-wrapper/react	Vite	910.78KB	225.92KB	-0.23%
react-p5-wrapper	Rollup	913.13KB	226.43KB	N / A

This is actually good news though because the Vite version is smaller without optimisations than the Rollup version which is highly optimised. This means in future releases we can expect smaller and more efficient bundles as we optimise the Vite output.

Again, these two bundles have the same version number since they have the same content being bundled, there is no difference between them besides the build tool being used. If you wish to migrate to the new package name already before the old name is marked as deprecated, this is a great time to do it.

[jamesrweb]

The package name migration is now complete and a deprecation message has been set on the old package name to inform users of the change. The deprecation message will show on NPM package views on the registry website and via CLI installs such as is seen in the screenshots below.