No longer working?

[bmcmurray]

Hi @rhodee, I can't seem to get this to work any longer, including running your example app.

No manifest or server worker gets registered and no metatags are injected.

Any insights?

razzle-plugin-pwa@2.2.3
razzle@2.4.0

[rhodee]

Hey @bmcmurray - let me look into this. The plugin itself could also use some updates to be more in-line with the plugin structure for Razzle. I will invest some time in this and get this looked at.

[rhodee]

Hey @bmcmurray I was unfortunately not able to reproduce your experience. I ran the npm run build command and that produced the expected manifests files (manifest.json, precache-manifest.*.json and sw.js) in the examples/build folder.

If you have a repo I can pull down to review, I'd be happy to continue investigating.

[calderaro]

had a similar issue the problem was "require.resolve(path.join(__dirname, 'public', 'favicon-16x16.png'))" failing without a message but that is on webpack-pwa-manifest

[sixman9]

@calderaro

Add const path = require('path'); to 'razzle.config.js', then supply your PNG files.

[msvargas]

In windows add path
....
const path = require("path");
const pwaConfig = {
swDest: path.resolve(__dirname, "build", "sw.js")
};

[lucasreppewelander]

i suppose i need to add these somehow to the server.js file? I suppose the files you're talking about needs to be able to go into the /static folder?

[lucasreppewelander]

I did somehting like this to get it inside my server.js html:

<link rel="manifest" href="${
	assets[''].json.filter((i) =>
		i.includes('manifest')
	)[0]
}" />

a bit hacky but dunno if theres another way?

[rwehresmann]

@lucasreppewelander you could use const fs = require('fs') and

${fs.existsSync(`${process.env.RAZZLE_PUBLIC_DIR}/manifest.json`) && '<link rel="manifest" href="/manifest.json">'}