fix(js): ensure js libraries' build produce esm output in ts solution setup#29546
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
View your CI Pipeline Execution ↗ for commit 4d49725.
☁️ Nx Cloud last updated this comment at |
bc23be2 to
3f97d26
Compare
3f97d26 to
4d49725
Compare
| const allDiagnostics = ts | ||
| .getPreEmitDiagnostics(program as Program) | ||
| .concat(result.diagnostics); | ||
| const allDiagnostics = options.ignoreDiagnostics |
There was a problem hiding this comment.
Makes sense for correctness. We should look at it again in the future to see if want to allow builds without typechecks, maybe a separate typedefs task for swc and esbuild so users that do not need d.ts files don't need to pay the penalty.
|
Failed to publish a PR release of this pull request, triggered by @leosvelperez. |
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
esbuild,swc, andtscto produce ESM output when using the TS solution setup.esbuildandswcexecutors so they generate declaration files even when skipping type-checking.cjsandctsto theignoredFilespattern for the rollup config file in the eslint config.Current Behavior
Expected Behavior
Related Issue(s)
Fixes #