Joel Gallant

We use yarn for the monorepo, I imagine the issue is npm works differently? We do check that the vite plugin works in CI

In general all npm packages are consumable by any package manager. But within our repo, we have the monorepo setup using yarn. So for your own repos, you can definitely...

I can give it a look over the weekend for sure. I havent paid close attention to vite release since first writing the plugin, so an issue with hot reloading...

Just for the record, I was able to repro this as described in a clean vite project. Will try and get a fix out today if I can find the...

Yeah, this is somewhat trickier than I thought. The plugin system doesn't work consistently between dev and prod builds, and plugin API has changes a bit from v2 and v3....

Hey thanks! I don't know very much about the NextJS build pipeline. But it sure sounds like a plugin we could build, similar (if not using) to the webpack plugin....

> [the index file](https://github.com/launchcodedev/app-config/blob/master/app-config-webpack/src/index.ts#L3) still tries to import from the library Oh! The import there makes sense, I didn't notice that. So a lazy load instead would likely work.

@gregnr I'm getting somewhat close to a release candidate for 3.0, it would be ideal to coordinate with LC to onboard

I haven't used NextJS a lot, but support for it seems like a win to me!

#53 basically provides this out of the box. It's not exactly plug-n-play though (for example, non-text Content-Types don't tend to work). Would probably have to play with the http options...