eslint-plugin-nuxt | ESLint plugin for Nuxt.js | Code Analyzer library

I thought it was a glitch that had been caused by the upgrade, but this time the error was caused by the i18n settings in nuxt.config.js. After commenting it out, the docker command started as usual.

nuxt.config.js

Problem solved with ternary if:

Element+ is a Vue3 UI library, so it is indeed not compatible with Nuxt2 (using Vue2). Hence why you're getting the error: it is not retro-compatible with Vue2.

Meanwhile, Element is totally compatible with Vue2 and may be a good-enough fit.

Do you need to use exactly this one btw? There is a lot of choices when it comes down to CSS frameworks compatible with both Vue2 and Vue3. Not all of them are, but most do.

When you do use privateRuntimeConfig, your env variable will only be available on SSR. Hence the first time you do reach the page, you do have access for it.

Then, when you navigate (client-side only so), you do not have access to it anymore on your client. As explained in the official documentation.

Sanity's documentation is talking about the privateRuntimeConfig, meanwhile I do wonder if their token is aimed only for SSR or not. Usually, you do have a public token that you can expose through the publicRuntimeConfig key.

There is a headless channel on Discord that is available here: https://discord.gg/H4hJBMCK
Otherwise, posting a Github issue will probably lead you to an answer from Daniel.

But it is possible that Sanity is aimed at fetching the content on server only, not sure.

There is a setToken method but it this one is aimed at using req only, it means that this is not suited towards a target: static build?

EDIT: nvm Ovi achieved to make it work as shown here: https://github.com/nuxt-community/sanity-module/issues/99#issuecomment-813993013
This one should probably work!

PS: was kinda writing as I was looking into the issues. Sorry if it's a bit messy. Tell me if the latest solution works and I'll edit my answer.

Try changing your start script to be a path to nuxt/bin then provide the

Optionally if you still are having issues, consider adding the -c flag with the relative path to your nuxt.config.js file.

Do the same for build.

Nuxt is only compatible with Vue2 as lf right now. Even if you use @nuxtjs/composition-api, this will not change the way the template is compiled (it is still Vue2 at the end of the loop).

The latter package only enables the use of composition API, this is not actually Vue3.

EDIT: updating the build command fixed OP's issue.

Do you even need the vercel.json here?
I've tried to host one of my repo there and it's working fine with those settings only.

Hosted there: https://nuxt-tailwind-typography-darkmode-boilerplate.vercel.app/

Vercel pretty much self-detected that it was a Nuxt project and almost aced it itself.

I solved the issue by creating a plugin that reload the page when new pwa version is released

Plugins folder

"start": "cross-env PORT=8080 nuxt start",

Why you add cross-env command in package.json files?

First of all, we need to clarify what problem cross-env solves and was born. Mainly to solve the problem of environment variables under windows. And your webapp is deployed under linux, the current problems, after my attempts, I initially think that we do not have sudo permissions, can not install cross-env globally.

Then in azure, only ports 80 and 443 are supported, cross-env PORT=8080 nuxt start, even if the dependencies of cross-env exist in the linux environment, an error will be reported. Because the specified port 8080 is not supported.

So just remove cross-env PORT=8080 .

In package.json.