Ts6 - #107
Conversation
…ly 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.
…ild script in package.json
The problem stems from the requirement of Node.js of "rewriteRelativeImportExtensions" to be "true".
This causes any import that refers to the package name ("@specs-feup/lara/...") to throw a compilation error when compiling Lara-JS.
However, if we rewrite them to use relative imports, the Jest config in the downstream weavers will error out.
Thus, we added directives for the Typescript compiler to ignore the errors in these particular lines.
The ignore directives were of the appropriate scope as to avoid compilation errors in Lara-JS and in the downstream weavers' compilations.
|
![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: 691df915ed
ℹ️ 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.
When an existing consumer imports a previously published path such as @specs-feup/lara/api/lara/util/Accumulator.js, this pattern captures lara/util/Accumulator.js and resolves it to api/lara/util/Accumulator.js.ts, which does not exist. Under Node 24.15 this produces ERR_MODULE_NOT_FOUND; the repository's legacy scripts still use these .js specifiers (for example LARAI/resources/larai/test/api/AccumulatorTest.js), and Weaver.executeScript() loads such scripts with native import(), outside Jest's mapper. Add explicit .js compatibility patterns mapping to the corresponding .ts files before publishing the native-TypeScript package.
Useful? React with 👍 / 👎.
No description provided.