-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
esbuild
,swc
, andtsc
to produce ESM output when using the TS solution setup.esbuild
andswc
executors so they generate declaration files even when skipping type-checking.cjs
andcts
to theignoredFiles
pattern for the rollup config file in the eslint config.Current Behavior
Expected Behavior
Related Issue(s)
Fixes #