Bjorn Lu

> I think we could send back a message to the server saying that this file caused reload (like with invalidate) so that even without hmr debug on you can...

I think most browsers will default to show debug logs, so it shouldn't get hidden in most case unless they explicitly hide it. The vite connection messages are also debug...

If you're accessing the exported names within a circular dependency loop on initialization, it could trigger an error. If they're lazily referenced, usually it will work. If you did hit...

Is there a reason you want a page reload? HMR should kick in instead so you'd see the changes. If HMR didn't kick in and it didn't cause any errors...

I think it would be best if you can open a new issue for it with a repro of the problem. Depending if this is used for react/vue/preact etc, it...

Seems like it's coming from Rollup. It's likely not a bug in `@material/ui`. Linking Rollup locally, the error is coming from [here](https://github.com/rollup/rollup/blob/1df8b4924f014e0cabd4c0364370801a658cc489/src/Module.ts#L1128-L1136). The original error is this: ```js { code:...

There's not much to be fixed in Vite if I understand the issue. Someone would need to debug what happens in https://github.com/rollup/rollup/blob/1df8b4924f014e0cabd4c0364370801a658cc489/src/utils/getOriginalLocation.ts#L10-L27 that's causing the error. Maybe it's a bug...

[`build.lib.entry`](https://vitejs.dev/config/build-options.html#build-lib) accepts an array or object that can be used to configure multiple entrypoints. We could add an example configuration in the Library Mode section you linked. > Does this...

@DiFuks I think that's related to https://github.com/vitejs/vite/issues/15300. It's currently not possible to process the injected `__vite__mapDeps` as Vite only has the dependency information post-build.

LGTM 👍 Let's maybe wait for others to review or the next meeting to confirm if the priority order is fine.