7 Commits

Author SHA1 Message Date
Robin Malfait
c03f9ad600
Improve public API (#5526)
* introduce `public` folder

This can contain all of the `public` functions we want to expose.
This will be a bit nicer for example when you want to use
internal/private functions (we use some in the vscode intellisense
plugin).

* use public `resolveConfig` function

* expose resolveConfig in the root

This will use the resolveConfig we expose from the `public` folder. We
can probably generate these as well.

* make `colors` public

* make `default config` public

* make `default theme` public

* make `create plugin` public

* update to public paths

* remove `@tailwindcss/aspect-ratio` from tests

This should be tested in its own repo instead.

* remove `@tailwindcss/aspect-ratio` as a dependency

* drop `Build` step from CI

The build step is not a prerequisite anymore for running the tests. When
we want to release a new (insiders) release, the `prepublishOnly` step
will be executed for us.

Before this change, it would have been executed twice:
- Once before the tests
- Once before the actual release

* improve paths for caching purposes

* add pretest scrip for generating the plugin list

Now that we can use `SWC`, automatically generating the plugin list
before running the tests is super fast and you don't even have to think
about it anymore!
2021-09-26 12:44:13 +02:00
Robin Malfait
4142b3fbaf
setup npm registry url
The `NPM_TOKEN` name was also incorrect (surprise?). Found another
resource here that mentions the `registry-url` option and
`NODE_AUTH_TOKEN`. Let's see if that works...

https://docs.github.com/en/actions/guides/publishing-nodejs-packages
2021-09-07 15:58:32 +02:00
Robin Malfait
fac02f3de9
use the correct token name
I used `NODE_AUTH_TOKEN` in other projects but that doesn't seem to work
anymore for some reason 🤔

Found this resource that talks about `NPM_TOKEN`: https://docs.npmjs.com/using-private-packages-in-a-ci-cd-workflow
2021-09-07 15:52:17 +02:00
Robin Malfait
016eaa5091
Add --no-git-tag-version flag (#5426)
When you run `npm version`, it also tries to make a git commit and a git
tag. However, we are not doing anything with this and CI doesn't know
who the committer is.
2021-09-07 14:45:03 +02:00
Robin Malfait
2b9c4fec1f
Force creating an npm version for insiders build (#5423)
This fails because we usually use node 14 or 16, which has a
package-lock.json version of `2`. However on node 12, this version is
`1`. This means that after an npm install the package-lock.json is
touched and thus `npm version` fails because git is in a dirty
directory.

Adding a `--force` is not ideal, but also not really an issue since the
only thing that could change is the package-lock.json and this is not
published to npm anyways.
2021-09-07 14:30:55 +02:00
Robin Malfait
d01091d44d
Improve release workflows part 2 (#5422)
* ensure we build before the tests

Our tests require that for now. Will probably improve this in the
future.

* improve insiders version name

This will make it consistent with previously published versions.
2021-09-07 14:18:22 +02:00
Robin Malfait
7c9bc49259
Add automated release/npm publish workflows (#5421) 2021-09-07 14:13:21 +02:00