Add @tailwindcss/browser package

[thecrypticace]

We're going to publish the CDN / browser build of v4 as an npm package so it can be loaded from things like unpkg. This sets up the package for that. The CDN is still intended only for development use. Please do not use it in production.

Note: like the v3 CDN, since it reacts to changes in the DOM, some things like transitions can break if the transition relies on the class being defined before being added to the DOM for correct behavior.

[thecrypticace]

@RobinMalfait Is there anything special I need to do to make sure publishing will work?

[RobinMalfait]

@RobinMalfait Is there anything special I need to do to make sure publishing will work?

Nope should be good! We publish via pnpm which uses the workspaces, so as long as they are setup it should be good. The only other thing is if we publish additional packages that need to be in sync with the @tailwindcss/browser version, but that's not the case so should also be fine. Otherwise we would've to edit the version-packages script.

You can run pnpm --recursive publish --tag next --no-git-checks --dry-run to test it (note: this only results in output for packages that need to be published. Already published packages will not show up and will be a no-op)

[philipp-spiess]

Pretty impressive how simple the code for this is. 👏

[RobinMalfait]

Looks nice, I like the performance marks as well

[RobinMalfait]

Can/should we merge these? I think we can use --filter twice 🤔

[thecrypticace]

If you do that it does some super super weird stuff to the console output

[RobinMalfait]

Just tried it, that is … interesting 😂