> @kirkrodrigues / @davemarco
>
> Any objection if we [`npm unpublish`](https://docs.npmjs.com/cli/v9/commands/npm-unpublish) 0.3.1 and 0.3.2 (see #48) on the npm registry?
No, go for it.
One optional comment otherwise lgtm.
For the PR title, how about:
```
ci(publish-to-npm): Download and extract build as single artifact at the correct path (fixes #48).
```
One optional comment otherwise lgtm.
For the PR title, how about:
```
ci(publish-to-npm): Download and extract build as single artifact at the correct path (fixes #48).
```
One optional comment otherwise lgtm.
For the PR title, how about:
```
ci(publish-to-npm): Download and extract build as single artifact at the correct path (fixes #48).
```
For the PR title, how about:
```
build(cmake): Extract CMake project name and version from package.json.
```
It's subjective, but I think `build` is a more appropriate type since this chang...
> but yeah why don't we directly change the metadata in package.json and let cmake sync from it? lol
Yep.
> with that said, realistically, in this project, those variables are not getting ref...
> Alternatively, shall we look into turning this into a Vite-React app? That way we don't have to manage the build configs on our own with webpack.
We could, I guess.
Yeah, that's my understanding based on this: https://webpack.js.org/configuration/configuration-types/#exporting-a-function
I think the old code was wrong since it should've been using the `env`...
```suggestion
BreakConstructorInitializers: "BeforeColon"
BreakFunctionDefinitionParameters: false
```
This is a new option that's unfortunately omitted from the release notes.