Why do I always get 502?

[rowild]

This sandbox:
https://codesandbox.io/s/quasar2vue3setup-forked-u2siof
(first linked to a github repo, then forked)
only yields 502. I have no idea why. Locally it works perfect.

Any ideas?

[JamesACS]

Hey @rowild - I'm seeing this error appear:

error @quasar/[email protected]: The engine "node" is incompatible with this module. Expected version "^18 || ^16 || ^14.19". Got "14.18.1"
error Found incompatible module.

Where did you fork the sandbox from?

[rowild]

Thank you for our feedback, @JamesACS !

It's been a while - I didn't fork the repo, but create it on my own, commit it to github (were I can't find it anymore) and then "forked" (copied it over) to codesandbox.

Do you happen to know, why a Node version is selected that does not fit? The quasar.config.js file clearly states that a Node v16 should be used:

   build: {
      target: {
        browser: ['es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1'],
        node: 'node16'
      },

Also, changing the node version in package.json does not improve the situation...

[rowild]

Here are screenshots:

[rowild]

It also seems that <script setup> is recognised as JSX code...

[JamesACS]

Hey @rowild - I'm not seeing any issues now - did you manage to resolve the problem?

[rowild]

@JamesACS Thank you for asking, but no. The squiggly lines, as shown in the previous screenshot, are still there. No idea how to fix that. Do you have an idea?

[JamesACS]

@rowild - I've been looking into this but haven't found a solution, the error is being thrown by our ESLint integration but doesn't seem to affect functionality.