Ts6 - #246
Conversation
…nly erasable syntax is allowed - Removed a couple of deprecated files. - Transformed enums into "const" declarations. - Modified the tsconfig.json files - Updated to TS 6 while I was at it.
Since we do not transpile TS anymore, the sources have been moved to their old destination folders.
…uild script in package.json
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a8c215e87b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "exports": { | ||
| "./api/*.test.ts": null, | ||
| "./api/*.config.ts": null, | ||
| "./api/*": "./api/*.ts", |
There was a problem hiding this comment.
For existing scripts that import paths such as @specs-feup/clava/api/clava/Clava.js, this wildcard captures clava/Clava.js and resolves it to the nonexistent ./api/clava/Clava.js.ts. This affects dozens of checked-in ClavaWeaver resource scripts and is reproducible with Node 24 before the target module is loaded; add an explicit ./api/*.js-to-./api/*.ts mapping (and the equivalent for code) or continue publishing compiled .js files.
Useful? React with 👍 / 👎.
| # Only on ubuntu-latest | ||
| - name: Publish JS | ||
| if: matrix.os == 'ubuntu-latest' && matrix.node-version == '22.x' | ||
| if: github.event_name == 'push' && github.ref == 'refs/heads/staging' && matrix.os == 'ubuntu-latest' && matrix.node-version == '25.x' |
There was a problem hiding this comment.
For a release push to refs/heads/master, this condition now skips the only repository workflow containing npm publish; the remaining command publishes staging prereleases under the staging tag only. Consequently, even a master commit with a deliberately bumped package version can no longer publish the stable latest package as the previous branch explicitly did.
Useful? React with 👍 / 👎.
No description provided.