Unfortunately, it’s not possible to intercept the `await import(…)` used
by newer versions. This means the Standalone CLI will not be able to
load ESM postcss config files. You still will using the npm package and
newer versions of Node.js.
This PR fixes some package vulnerabilities that you will see when
running `npm install`. This PR fixes that by bumping dependencies to get
rid of the vulnerabilities.
* CI: Add provenance to all published packages
This commit adds provenance for all published packages. See the NPM documentation [0].
Provenance will allow people to verify that the tailwindcss packages were actually built on GH Actions and with the content of the corresponding commit. This will help with supply chain security.
For this to work, the `id-token` permission was added only where necessary.
[0]: https://docs.npmjs.com/generating-provenance-statements
* chore: Add missing repository links to packages
This is needed for provenance, to link the repository to the build accoring to the NPM docs [0].
[0]: https://docs.npmjs.com/generating-provenance-statements#prerequisites
* Add standalone-cli build for Windows ARM64
* Fix path to binary on windows
* Fix style
* Simplify Windows mapping in standalone CLI tests
Co-authored-by: Jordan Pittman <[email protected]>
* Update deps
* Fix usage of postcss config file in standalone CLI
The config file created with `--postcss` would fail because we didn’t stub require to load `tailwindcss` or `autoprefixer` when we should.
* Update tests
* WIP
