You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
svelte-migrate currently gives the option to select paths to be migrated, but those are only first-level child directories. I'd like to be able to specify paths to explicitly ignore.
When is this useful?
I've recently came across this when trying to migrate to svelte@5 while using shadcn-svelte - a library which saves components to the src/lib/components and migrating them may not be the desired behaviour.
A good approach to avoid any clutter in the cli would be to use an optional argumen/option when running sv migrate to explicitly ignore certain paths.
The text was updated successfully, but these errors were encountered:
This adds two new prompts to the Svelte migration:
- custom folder prompt (from multiselect); if selected you can specify what folders exactly to migrate. closes#390
- adds a way to skip migrating your components if you want to do it incrementally but still benefit from having your package.json and entry points migrated automatically
svelte-migrate
currently gives the option to select paths to be migrated, but those are only first-level child directories. I'd like to be able to specify paths to explicitly ignore.When is this useful?
I've recently came across this when trying to migrate to
svelte@5
while using shadcn-svelte - a library which saves components to thesrc/lib/components
and migrating them may not be the desired behaviour.A good approach to avoid any clutter in the cli would be to use an optional argumen/option when running
sv migrate
to explicitly ignore certain paths.The text was updated successfully, but these errors were encountered: