Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add a version comment to the mockServiceWorker.js
See original GitHub issueIs your feature request related to a problem? Please describe.
When the mockServiceWorker.js in the public folder is updated it is not clear if this is by mistake or an upgrade to a new version.
Describe the solution you’d like
Add a comment near the top of the mockServiceWorker.js file with the npm package version that produced the file in the public directory. This would make it more discoverable which version of the file you have and it will be easier when updating.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Agree. At the moment we still recommend committing the worker script to VCS to give the developer the power over that script. It’s just a JavaScript module like any other. This transparency is a vital part of the security view on MSW.
That’s a good question. I guess I would prefer to have the script explicitly visible in the public directory. But I see the other way working fine for some situations as well. Don’t have a strong preference at the moment so, maybe, supporting both should be fine until a “best” practice is more clearly established, if ever.