-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: _vm._ssrNode is not a function #510
Comments
This sounds like a Vue issue rather than with Bridge. Would you provide a minimal reproduction? 🙏 |
Hmm, on Nuxt 2 it worked. I will try to create a reproduction. |
Ready! :) Preview package: cd ./package
yarn
yarn serve Build package: cd ./package
yarn
yarn build
yarn pack Run cd ./nuxt2
yarn
yarn dev Run cd ./nuxt-bridge
yarn
yarn dev |
@danielroe I would have another request. Could you take a look why I don't have types for the ~/plugins/hello1.ts import { defineNuxtPlugin } from '#app'
declare module '#app' {
interface NuxtApp {
$hello1 (msg: string): string
}
}
declare module '@vue/runtime-core' {
interface ComponentCustomProperties {
$hello1 (msg: string): string
}
}
export default defineNuxtPlugin(({ provide }) => {
provide('hello1', (msg: string) => `Hello 1 ${msg}!`)
}); ~/plugins/hello2.ts import { defineNuxtPlugin } from '#app'
declare module '#app' {
interface NuxtApp {
$hello2 (msg: string): string
}
}
declare module '@vue/runtime-core' {
interface ComponentCustomProperties {
$hello2 (msg: string): string
}
}
export default defineNuxtPlugin(({ provide }) => {
provide('hello2', (msg: string) => `Hello 2 ${msg}!`)
}); ~/tsconfig.json {
"extends": "./.nuxt/tsconfig.json",
"compilerOptions": {
"target": "ES2018",
"module": "ESNext",
"moduleResolution": "Node",
"lib": [
"ESNext",
"ESNext.AsyncIterable",
"DOM"
],
"esModuleInterop": true,
"allowJs": true,
"sourceMap": true,
"strict": true,
"noEmit": true,
"experimentalDecorators": true,
"jsx": "preserve",
"baseUrl": ".",
"types": [
"@nuxt/types",
"@types/node",
"@vue/runtime-core"
]
},
"exclude": [
"node_modules",
".nuxt",
"dist"
]
} Reproduction: yarn
yarn dev |
It also started breaking for me as well
|
@MartinX3 That indicates an old version of |
@danielroe I already removed the lock file and it uses |
I am able to reproduce this by creating a new Nuxt 2 project and then following the Nuxt Bridge upgrade guide. The only package I have added is the https://v3.nuxtjs.org/bridge/overview/ Here is the runtime error
|
After replace |
This sounds like it might be an issue with https://github.com/nuxt-community/nuxt-property-decorator in that case. |
The main contributor of |
@Laruxo it's deprecated by the composition api since vue 2.7. |
It has not responded for a while, so I am closing it. |
Environment
Nuxt 2 with
@nuxt/bridge
.Reproduction
Unfortunately the package is secret so I can't create a reproduction.
Describe the bug
After moving from
@nuxtjs/composition-api
to@nuxt/bridge
, I get the error:<F24Loader />
is a component from the company's npm package (written with rollup, in Vue 2) in which we keep components common to all projects. It helps to setssr: false
innuxt.config.ts
file, or wrap a component in<client-only>
. Is there a chance that these components will also work on the server side?Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: