Preact build not copying over manifest.json and assets
See original GitHub issueDo you want to request a feature or report a bug? Bug
What is the current behaviour?
When using preact build --no-prerender
, the manifest.json
and assets/*
files get replaced with the default template ones.
If the current behaviour is a bug, please provide the steps to reproduce. I’m using the typescript template. I only added an additional build flag in the package.json file.
What is the expected behaviour?
I’m assumed my manifest.json
file would be copied over.
Please mention other relevant information. I’m using the latest Preact X.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Preact Chrome extention Manifest warning regarding icons type
Setting up a Preact Chrome extension and getting a warning of Manifest: property 'icons' ignored, type array expected.
Read more >preact-cli | Yarn - Package Manager
- No longer copies 'sw-debug.js' to output directory on prod builds. No functional changes, as it was not used. ... ab84275 #1434 Thanks...
Read more >vite - npm
The vue , react and preact templates of create-vite-app all come with HMR out of the box. ... production build. Never-referenced assets will...
Read more >API - esbuild
The build API call operates on one or more files in the file system. ... so on) will also be inlined. By default...
Read more >How to Create a PWA Game Using Preact in 5 Steps · Tutorial
manifest.json. ├── routes. └── style. assets will contain our assets (favicon and other icons); components will have our preact ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is my temporary fix in package.json
Basically I copy manifest.json and the icon into the build folder
@prateekbh I can see the original
manifest.json
file (the one that was there when the project was generated).I’m using
3.0.0-next.19