vike: manifestKeyMap error throwed after version upgrade
Description
After package version bump facing issue with Cloudflare workers deployment.
Uncaught (in promise) TypeError: Cannot set property manifestKeyMap of #<Object> which has only a getter
Error Message + Error Stack
Object.assign(obj, objAddendum);
^
at objectAssign
(/Users/u/Projects/frontend/node_modules/.pnpm/vite-plugin-ssr@0.4.69_vite@3.2.5/node_modules/vite-plugin-ssr/dist/cjs/utils/objectAssign.js:6:11)
at assertPluginManifest
(/Users/u/Projects/frontend/node_modules/.pnpm/vite-plugin-ssr@0.4.69_vite@3.2.5/node_modules/vite-plugin-ssr/dist/cjs/node/plugin/plugins/manifest/assertPluginManifest.js:15:30)
at initGlobalContext
(/Users/u/Projects/frontend/node_modules/.pnpm/vite-plugin-ssr@0.4.69_vite@3.2.5/node_modules/vite-plugin-ssr/dist/cjs/node/globalContext.js:41:57)
Current version: /vite-plugin-ssr/0.4.69_vite@3.2.5:
Previous version: /vite-plugin-ssr/0.4.54_vite@3.2.4:
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (10 by maintainers)
Commits related to this issue
- fix: workaround immutable exports (fix #596) — committed to vikejs/vike by brillout a year ago
I know, still, it seems like something funky on Cloudflare’s side.
Actually, I’ve an idea why this can be. I’ll have a look at it later today.