react-progressive-web-app | opinionated React based repository | Frontend Framework library
kandi X-RAY | react-progressive-web-app Summary
kandi X-RAY | react-progressive-web-app Summary
What is this repo? Well, it's a very opinionated React based repository which is optimized for Progressive Web App development. In its current format, it will hit around 95-100 out of 100 when running through the Lighthouse audit. You can test this out by visiting the demo and generating a lighthouse report against it. There are many different ways to structure an application; this repository is the way that I tend to structure my applications. I think, you could strip out the webpack.config.js file, tweak it slightly and then you will be on your merry way. But, you would still need to create a manifest, upload the images and make sure they are referenced correctly, that is why I decided to open source this repo as it will allow you to just write React code without worrying about painful configuration.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of react-progressive-web-app
react-progressive-web-app Key Features
react-progressive-web-app Examples and Code Snippets
Community Discussions
Trending Discussions on react-progressive-web-app
QUESTION
I deployed a production Angular 9 application on S3 + cloudfront. It works very well but I've some problems every time I release a new update of the application. I read many articles:
- https://medium.com/@sumn2u/react-progressive-web-app-s3-and-cloudfront-6c890fa873fb
- https://medium.com/driven-by-code/on-the-importance-of-correct-headers-and-metadata-in-s3-origins-for-aws-cloudfront-50da2f9370ae
I set right caching for index.html and ngsw-worker.js so they are not cached from cloudFront. Every Angular deploy is saved on S3 on a new folder with the build number, like this:
After I do this, I change the directory name of CloudFront in order to point to the new location. Unfortunately, doind this create several problems to customers that have previous version of the application. In fact if the service worker didn't get the update when the user load the application, if the user load some part of the application that were not cached before, I get a error loading chunk (because it doens't exist anymore on S3).
So I'm wondering what's the best way to continuosly deploy an Angular application on AWS S3 + CloudFront. Am I supposed to load all files inside the same folder? Isn't it too inefficient (very soon I'll have thousands of files)? Any hint is really appreciated.
...ANSWER
Answered 2020-Jul-14 at 06:36You can do following :
- Directly deploy build folder to S3 bucket.
- Not required to cached
index.html
file - Whenever you deployed or upload build to S3,do the following step
- Go to cloudfront
- Do invalidation of objects
- Create entry /*
For continuous deployment you can write script using boto3
of aws for automatically invalidate cached once folder uploaded successfully.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install react-progressive-web-app
Install dependencies:
Run the unit tests
Run the e2e tests
Run the static type checker
Start the webpack server
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page