Closed dummdidumm closed 1 year ago
You might want to add another bullet point to consider switching from yarn v1, which has frozen development for a while, to e.g. pnpm (which would be in line with the package manager choice of other sveltejs repos). That's not a semver issue though.
This issue is intended to collect breaking changes we want to do for the next major version of svelte-preprocess. What currently comes to my mind:
I was hoping v5 would be released at a similar time as the RFCed new preprocess API, but it seems that's still far from happening. Removing deprecations and support for EOL node versions is a good start! We don't need to make it a very big breaking change 🤷
You might want to add another bullet point to consider switching from yarn v1, which has frozen development for a while, to e.g. pnpm (which would be in line with the package manager choice of other sveltejs repos).
I have no qualms with switching to another package manager, even more, if it's to the same one used by other Svelte projects.
Peer dependencies can be marked optional as shown here: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#peerdependenciesmeta
I believe this turns off the automatic installs.
This issue is intended to collect breaking changes we want to do for the next major version of
svelte-preprocess
. What currently comes to my mind:lang="typescript"
andtype="text/..."
(deprecated already AFAIK)