Preset for Next.js, TypeScript, and CSS Modules about presets

[shilman]

That's awesome @justincy! Is there any way to decouple it, so that a user could install preset-typescript (possibly updated by you) and preset-css-modules (doesn't exist yet, you'd contribute it) and achieve the same result? Or could it not work that way?

[justincy]

I'm not an expert in this area, but as far as I can tell, the existing preset-typescript is not compatible with Next. Next actually provides its own babel preset which is the easiest way to get TypeScript working for Next (it's included in the Storybook preset here). I think the issue with preset-typescript has to do with how Next doesn't require React to be imported in files that use JSX. For now I could create preset-next-typescript until someone with more expertise figures out whether there's a way to merge it into preset-typescript.

I see the benefit of creating the preset-css-modules. I guess there's no reason it needs to be coupled with preset-next-typescript.

[SpencerDuball]

As far as not including preset-css-modules with the preset-next-typescript goes, Next 9.2 allows for css modules to be imported within the _app.(jsx|tsx) out-of-box. I think a seperate package for preset-css-modules would be nice for people with other applications, but having that preset as well included by default in any Next preset (typescript or javascript) might mitigate some headaches. That way the most manual work after installing a Next preset would be importing your global css files to something like the preview.js file in your gist.

Additionally, the _app.(jsx|tsx) file will always be in the same spot in a Next project's file hierarchy so maybe there is a small script that could scan for import statements ending with .css too?

[shilman]

We have a specific preset for CRA that basically tries to reuse a users CRA settings to match their app setup as closely as possible, no matter the config (js, ts, etc). I’m wondering whether the same thing might be possible for Next? Cc @mrmckeb

[mrmckeb]

So I was thinking about Next and Gatsby recently.

The problem is that both have plugin architectures, so we'd have to think about how we support those too - this is particularly important with Gatsby - which has a large plugin ecosystem.

That being said, I think we could support the 'defaults' with presets. We could also reach out to the maintainers and see if they'd be interested in supporting the presets - as ultimately that is a goal of presets I think (@shilman).