9f647f311f
### What? Adding packages from the Effect ecosystem to the list of optimized-by-default imports ### Why? Effect usage includes very liberal use of `import * as Module from "effect/Module"` and `import { Module } from "effect"`. This is usually trees-shaken but in nextjs we must declare it to be optimized to be have this way. To provide a better experience to users I added all the packages in the ecosystem to the list that are possibly relevant. I don't expect all of them to get in, but the proposal should start from the full set of possible candidates. Not included are `/cli`, `/printer`, `/printer-ansi`, and `/vitest`. At the very least `effect` and `/schema` should be added for their prevalence, but even if there is hesitance I recommend adding `/platform` and `/platform-node` since it's natural for effect usage to grow into benefitting from these quickly enough. Related issue in the effect repo https://github.com/Effect-TS/effect/issues/2701 cited source for taken action: [the vercel blog](https://vercel.com/blog/how-we-optimized-package-imports-in-next-js) ### How? Adding strings to a set Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
---|---|---|
.. | ||
create-next-app | ||
eslint-config-next | ||
eslint-plugin-next | ||
font | ||
next | ||
next-bundle-analyzer | ||
next-codemod | ||
next-env | ||
next-mdx | ||
next-plugin-storybook | ||
next-polyfill-module | ||
next-polyfill-nomodule | ||
next-swc | ||
react-refresh-utils | ||
third-parties |