-
-
Notifications
You must be signed in to change notification settings - Fork 91
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: empty chunks #566
fix: empty chunks #566
Conversation
import { defineConfig, type Options } from 'tsup' | ||
|
||
export const commonOptions = { | ||
clean: true, | ||
clean: false, |
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.
this can probably be removed, it's false by default 👀
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.
ok (I added it explicitly to avoid reverting the flag)
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.
Thanks a lot!
This broke the docs generation |
different dts chunks are being generated because of splitting types entry in tsup. I think it's fine to leave 0 byte dist/types.js because it cannot be imported anyway. |
This PR also includes:
./types
subpackage export: should export only types, there is no implementationdata-loaders/*
intypesVersions
: node10 types brokenclient
fromtypesVersions
.I'm going to check on my local Windows laptop the error with long paths in Nuxt.
We split tsup options to generate only dts for
src/types.ts
(thx for the help @brc-dd)