-
-
Notifications
You must be signed in to change notification settings - Fork 56
fix(cli): export types & switch to tsdown #719
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 3c815a2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
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 looks great! for some reason, i'm unable to push some changes to this pr, so i've added some suggestions below.
".": "./index.ts", | ||
"./css": "./tooling/css/index.ts", | ||
"./html": "./tooling/html/index.ts", | ||
"./js": "./tooling/js/index.ts", | ||
"./parsers": "./tooling/parsers.ts" |
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.
we'll have to keep in mind that @sveltejs/cli-core
will be a public package in the future, so this will have to be updated back to its original state when community add-ons are released
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.
Will it be @sveltejs/cli-core
or maybe under sv
like sv/core
?
What about @sveltejs/create
& @sveltejs/addons
?
It might be a question for later anyway
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.
Will it be
@sveltejs/cli-core
or maybe undersv
likesv/core
?
its still TBD, but our plans were to have core
be its own standalone package so that community add-ons don't have sv
as a direct dependency
What about
@sveltejs/create
&@sveltejs/addons
?
create
should probably stay in sv
, but there's an argument to be made as to where addons
should go. it may be more useful to have it be part of core
but we can figure it out when we get there :p
Thanks, types are coming through now! There are a few types that could be usefully reexported (TemplateType and LanguageType) to avoid What's significantly missing though is typed official addons - because they're exported as a list, there's no way have type-safe configured addons: cli/packages/addons/_config/official.ts Line 18 in 262ac80
Could we change this to export const officialAddons = {
prettier,
eslint,
...,
} satisfies Record<string, AddonWithoutExplicitArgs> as const; or similar? That way a user will be able to define, in a type safe way, a set of preconfigured options for the addons. |
I should not have created the PR! that's why we can't push there. :/ (TIL!) EDIT: it seems that you can push now @AdrianGonz97 |
Co-authored-by: CokaKoala <[email protected]>
Co-authored-by: CokaKoala <[email protected]>
Before exporting this, we need to fix Who wants to crack the matrix ? :D |
Well I thought I'd fixed |
Of course, Rolldown supports it. |
Something in my current toolchain (via |
Converted to draft, dosn't seem ready yet according to the comments |
exposing the atm, i'm trying to disable
i have a feeling this may be a |
i guess we could keep using with ideally, using |
No description provided.