You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm run dev fails on win11, what should i do to fix it?
win11
npm run deverror
> npm run dev
> [email protected] dev
> extension dev
✖︎✖︎✖︎ my-new-extension-32 compiled with errors in 1193 ms.
ERROR in [webpack-extension-target]
Path starts with "_" is preserved by the browser.
The browser will refuse to load this extension.
Please adjust your webpack configuration to remove that.
File(s) starts with "_":
_locales\en\messages.json
_locales\zh_CN\messages.json
but it works with npm run buildok
> npm run build
> [email protected] build
> extension build
►►► my-new-extension-32 compiled successfully in 249 ms.
►►► Building my-new-extension-32 extension using Chrome defaults...
.
├─ _locales\zh_CN\messages.json (2.16KB)
├─ _locales\en\messages.json (2.15KB)
└─ manifest.json (0.19KB)
Version: 1.0
Size: 4.50KB
Build Target: Chrome
Build Status: Success
Build completed in 0.25 seconds.
►►► No errors or warnings found. Your extension is ready for deployment.
ubuntu
npm run devok
> npm run dev
> [email protected] dev
> extension dev
►►► my-new-extension-32 compiled successfully in 7876 ms.
npm run buildok
> npm run build
npm run build
> [email protected] build
> extension build
►►► my-new-extension-32 compiled successfully in 913 ms.
►►► Building my-new-extension-32 extension using Chrome defaults...
.
├─ _locales
│ ├─ zh_CN
│ │ └─ messages.json (2.16KB)
│ └─ en
│ └─ messages.json (2.15KB)
└─ manifest.json (0.19KB)
Version: 1.0
Size: 4.50KB
Build Target: Chrome
Build Status: Success
Build completed in 0.91 seconds.
►►► No errors or warnings found. Your extension is ready for deployment.
The text was updated successfully, but these errors were encountered:
hi @xesam could you share the folder structure you are using/sample extension so I can try to replicate locally? I did some changes in the locales field, seems worth adding more tests to it
this is a message from an upstream dependency, so unless you do not have a folder starting with _ the message is expected. it works in production because the plugin works in dev mode only.
npm run dev
fails on win11, what should i do to fix it?win11
npm run dev
errorbut it works with
npm run build
okubuntu
npm run dev
oknpm run build
okThe text was updated successfully, but these errors were encountered: