-
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
web:rollup executor doesn't produce declarations with compiler set to swc #9059
Comments
I see this resolved in the latest Nx. Can you please retry with the latest version? In fact, I also see it resolved in If you do not see this resolved, can you please provide a repo so we can reproduce the issue? |
Hi @FrozenPandaz |
I'm having the same issue too. And from what I can see in the It seems like a missing feature so I thought the missed types in NX are expected. Not a big issue for compiling and bundling apps, but for libs that mean to be published to NPM, this is an essential feature. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Ping. Still relevant. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Still relevant |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
This issue still exists |
Still relevant. Had to change compiler to |
I also ran into this issue. Having to switch back to babel and lose my SWC performance improvements |
@FrozenPandaz would you consider removing the blocked tag that you added to this? This issue is still present in the latest version |
Same experience here with swc vs babel. |
Thanks for re-opening, @FrozenPandaz. What needs to be done to remove the blocked tag? Other people above have posted repros |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Still relevant. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Still relevant |
|
still relevant |
Based on the comment by @Chanki-Min, I've created a custom version of the rollup executor that includes the missing Just add these 4 files into a folder in your mono-repo, e.g. And then in the
It does generate the type declarations, but I'm not sure if there are other bad side-effects of this (will update this comment if I find any). |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
active |
this is still relevant |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
How it can be close, it is still relevant. without giving and reply and resulations, this thread closed multiple times. Dear team please provide the valid fix for this. bcs of this issue, me and my team are not able to directly use the nx, and in this case need to use babel instead of swc with webpack instead of NX !!!! |
Seems like nx contributers has busy days. I'm gonna make PR for this (in weekends?) |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Can this be solved? |
this issue fixed by #18342 cc @YonatanKra |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
When running
nx build
for my buildable library I don't getd.ts
files in the output directory.Expected Behavior
d.ts
files should be generated.Steps to Reproduce
--compiler swc
Environment
The text was updated successfully, but these errors were encountered: