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
Sometimes the generated package.json for the server contains invalid version specifier using | instead of || such as:
"ufo": "1.1.1 | 1.0.1",
"uuid": "8.3.2 | 9.0.0",
which then results in issues finding these modules:
Result: Failure Exception: Worker was unable to load function functions: 'Cannot find package 'ufo' imported from C:\home\site\wwwroot\functions\index.mjs' Stack: Error [ERR_MODULE_NOT_FOUND]: Worker was unable to load function functions: 'Cannot find package 'ufo' imported from C:\home\site\wwwroot\functions\index.mjs' at new NodeError (node:internal/errors:393:5) at packageResolve (node:internal/modules/esm/resolve:860:9) at moduleResolve (node:internal/modules/esm/resolve:909:20) at defaultResolve (node:internal/modules/esm/resolve:1124:11) at nextResolve (node:internal/modules/esm/loader:163:28) at ESMLoader.resolve (node:internal/modules/esm/loader:841:30) at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18) at ModuleWrap. (node:internal/modules/esm/module_job:76:40) at link (node:internal/modules/esm/module_job:75:36)
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Windows_NT
v19.4.0
3.1.1
2.1.0
yarn@3.3.0
vite
alias
,nitro
,ssr
,app
,css
,modules
,runtimeConfig
,routeRules
,tailwindcss
,graphqlServer
,content
,naiveUI
,vite
@nuxtjs/tailwindcss@6.4.1
,@huntersofbook/naive-ui-nuxt@0.6.0
,@pinia/nuxt@0.4.7
,nuxt-graphql-server@1.1.5
,nuxt-runtime-compiler@1.1.3
,@nuxt/content@2.4.3
,storybook-vue-addon/nuxt
-
Reproduction
No minimal reproduction yet, but here is a "big one": JabRef/JabRefOnline#1799
Describe the bug
Sometimes the generated
package.json
for the server contains invalid version specifier using|
instead of||
such as:which then results in issues finding these modules:
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: