pwa-module

pwa-module copied to clipboard

------------------------------
- Operating System: `Darwin`
- Node Version:     `v14.18.1`
- Nuxt Version:     `2.16.0-27264976.293dc11a`
- Package Manager:  `[email protected]`
- Bundler:          `Webpack`
- User Config:      `head`, `loading`, `css`, `serverMiddleware`, `plugins`, `modules`, `privateRuntimeConfig`, `publicRuntimeConfig`, `pwa`, `storage`, `axios`, `manifest`, `robots`, `auth`, `router`, `buildModules`, `webpackOptimisations`, `optimizedImages`, `build`
- Runtime Modules:  `portal-vue/nuxt`, `@nuxtjs/[email protected]`, `@nuxtjs/[email protected]`, `@nuxtjs/[email protected]`, `@nuxtjs/[email protected]`, `@nuxtjs/[email protected]`, `[email protected]`, `vue-currency-filter/nuxt`
- Build Modules:    `@aceforth/[email protected]`, `[email protected]`, `@nuxt/[email protected]`
------------------------------

There is issue with @nuxtjs/[email protected] with nuxt/bridge manifest file "_nuxt/manifest.0f2d95c2.json " not found on server.

Issue in nuxt bridge.In nuxt 2.15 its ok

@chz Do you have a deployment URL or repo i can check? That would be helpful to discover bridge issue quickly!

Its a private Repo. Maybe i can show you on the link where it is has problem.

@pi0, Can you check (LINK DELETED) i have opened for you for a one day.

@pi0, After checking please write here i must again close deployment url

@pi0 for reproduce just refresh page shift + command + r or hard reload

@pi0 any news?

You need config the 'publicPath'. pwa: { manifest: { publicPath: process.env.API_ENV === 'production' ? '{your cdn}' : '/_nuxt/', }, },

@Gaofancy i dont use cdn.

I had the same issue but it was after updating to Nuxt 3. Solution: run after build

cp .nuxt/dist/client/manifest* .output/public/_nuxt

any update on this issue it's not working after upgrading to '3.3.5'

By default IIS (and so the Azure App Service) doesn't serve .json files. You need to enable this feature in your web.config. If don't already have one, create it in the root directory.

More information can be found on this post: https://stackoverflow.com/a/52206106

Simple run the below command. I fixed the same issue using the below command

rm -rf dist && rm -rf node_modules && rm -rf package.lcok.json && npm i && npm run build After you just restart your server. I restart my pm2 server using the below command.

pm2 restart client