Skip to content

chore: undeprecate config.kit.files.* options#15482

Open
teemingc wants to merge 8 commits intomainfrom
chore-undeprecate-kit-files
Open

chore: undeprecate config.kit.files.* options#15482
teemingc wants to merge 8 commits intomainfrom
chore-undeprecate-kit-files

Conversation

@teemingc
Copy link
Member

@teemingc teemingc commented Mar 4, 2026

As discussed during the maintainer's meeting, this PR undeprecates the kit.files options. It also reverts the removal of mentions about these options in various parts of the docs done in #15343


Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.

Tests

  • Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

  • If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

  • Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

@changeset-bot
Copy link

changeset-bot bot commented Mar 4, 2026

🦋 Changeset detected

Latest commit: a9bfa71

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@sveltejs/kit Patch

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

@svelte-docs-bot
Copy link

Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep it hidden from the docs mostly, so that people don't stumble across it too much.
We also said that we wanted to keep it deprecated in the types along with an explanation that this is a "soft deprecation" in the sense of it's still supported but no longer recommended (use monorepos for most use cases instead)

Most importantly we need to revert the deprecation from the options parsing

@teemingc teemingc requested a review from dummdidumm March 4, 2026 13:18
@teemingc
Copy link
Member Author

teemingc commented Mar 4, 2026

Thanks! I made the changes but I'm unsure about the deprecation wording in the types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants