Anthony Fu

Server failed when reloading `nuxt.config.js` with Bridge Vite

1

### Environment ------------------------------ - Operating System: `Darwin` - Node Version: `v16.11.1` - Nuxt Version: `2.16.0-27282256.ab1c6cb4` - Package Manager: `[email protected]` - Bundler: `Webpack` - User Config: `buildModules`, `css`, `target`, `components`, `bridge`,...

Meta issue to track the progress from https://github.com/nuxt/framework/pull/1180 - [ ] ~~Update mocks with unenv~~ (~> nuxt/nuxt.js#12786) - [ ] Opt-in legacy - [ ] Hide invalid component name warnings...

feat: allow components to provide absolute import path

7

This would allow libraries to provide absolute import paths (from library submodules, or virtual modules) using the `components:extend` hook. In my case, I am integrating with `unplugin-icons`.

feat: use unplugin for loader

1

Use `unplugin` to support both Webpack and Vite, Using the logic from [`unplugin-vue-components`](https://github.com/antfu/unplugin-vue-components/blob/main/src/core/transforms/vue2.ts) to directly replace the component usage instead of local installation (make the codebase simpler and the runtime...

Support custom resolvers

1

Similar approach to https://github.com/antfu/unplugin-vue-components#importing-from-ui-libraries I been using this pattern for `unplugin-vue-components` for a while and I think it turns out a flexible and straightforward solution to support various component libraries...

Migrate to Nuxt 3

2

- [x] Rewrite to use `` and composition api - [ ] Break down index.vue - [ ] Check modules compatibility

Add a category for Vite

1

**Is your feature request related to a problem? Please describe.** We are having some great Vite resources recently and they are dissociated around in Github and communities, it would be...

Filter for breakpoints

Rules like `value-inferring`, `decimal`, `important prefix` etc.