markthree

我认为我们没有其他的时间来将它写成 admin，如果有感兴趣的小伙伴，欢迎提一个新的仓库

副本 #17

@lna1989 You can filter by hooks ```diff // nuxt.config.ts export default defineNuxtConfig({ devtools: { enabled: false }, extends: ["./layer"], + hooks: { + "app:resolve"(app) { + app.plugins = app.plugins.filter((p) =>...

> Yes, I also encountered this issue. Without making any changes to the code, upgrading to 3.10.2 only resulted in CSS appearing as if it had not been loaded when...

This is my reproduction, it only has the problem in 3.10.2, and can only be reproduced locally in node, not in stackblitz, so if anyone wants it, please download it...

I found out this is a problem with vite 🤣 Please add the following configuration to your package.json ↓ ```json { "overrides": { "vite": "npm:vite@latest" }, "resolutions": { "vite": "npm:vite@latest"...

@TutorFx A temporary solution is to add the following script to your `package.json` ```json { "scripts": { "prepare": "nuxt prepare", } } ``` Then remove your `yarn.lock` and re-execute `yarn`,...

@manniL Please add `prepare: "nuxt prepare"` to `packages/eorderbook-base/package.json` ```json { "scripts": { "prepare": "nuxt prepare" } } ``` Then re-execute the `pnpm install` command This is what triggers the generation...

> I don’t think run prepare everywhere is an elegant way to handle it. Yeah, that's what I thought. Maybe there is a better way, looking forward to other people's...

@martinszeltins I tested it and the package can't resolve the specific type from the relative paths for example  tip → This is because nuxt's internal unimport uses relative paths...