-
-
Notifications
You must be signed in to change notification settings - Fork 39
Description
Current behavior
When trying to build a vitepress Project with node version >25 and the vitepress-openapi. A lot of TypeErrors are thrown (always the same). This does not prevent the build from completing or the generated pages from working when deployed.
As far as I understand it, this is related to a change in the localstorage api from node. Node changed the Default behavior for the localstorage implementation
NodeJS Commit
Throw Error if path is missing
This leads to the issue, that a project builds without errors on NodeJS 24 and earlier. But throws errors when upgrading to NodeJS 25
Desired behavior
No errors should be thrown
Reproduction
No response
Steps to reproduce
Build a project with NodeJS >25
Logs and Error Messages
TypeError: n.getItem is not a function
at U (file:///home/pssi/GIT/iscan/docs/node_modules/vitepress-openapi/dist/OpenApi-B2KHkeoz.js:286:34)
at O (file:///home/pssi/GIT/iscan/docs/node_modules/vitepress-openapi/dist/OpenApi-B2KHkeoz.js:303:80)
at Ei (file:///home/pssi/GIT/iscan/docs/node_modules/vitepress-openapi/dist/OpenApi-B2KHkeoz.js:258:12)
at setup (file:///home/pssi/GIT/iscan/docs/node_modules/vitepress-openapi/dist/vitepress-openapi.client.es.js:58809:40)
at callWithErrorHandling (/home/pssi/GIT/iscan/docs/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:86:19)
at setupStatefulComponent (/home/pssi/GIT/iscan/docs/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:6383:25)
at setupComponent (/home/pssi/GIT/iscan/docs/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:6370:36)
at renderComponentVNode (/home/pssi/GIT/iscan/docs/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:398:15)
at renderVNode (/home/pssi/GIT/iscan/docs/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:529:14)
at renderVNodeChildren (/home/pssi/GIT/iscan/docs/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:545:5)
Other Information
No response