[Bug] CRA incompatibility on HTTPS=true flag
See original GitHub issueDescribe the bug
HTTPS=true
spits this error: EROFS: read-only filesystem, open '/node_modules/webpack-dev-server/ssl/server.pem'
after migrating to yarn 2.
To Reproduce
From a fresh CRA install, prepend HTTPS=true
flag in the scripts.start
from your package.json
.
It should now look like this
scripts: {
start: "HTTPS=true react-scripts start"
}
To clarify, yarn starts perfectly without HTTPS=true
, I’m suspecting webpack-dev-server
creates a self-signed certificate and writes it into its own directory, except they’re all now read-only.
Environment if relevant (please complete the following information):
- OS: OSX
- Node version v10.16.3
- Yarn version 2.0.0-rc.27
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (2 by maintainers)
Top Results From Across the Web
https://courses.cs.washington.edu/courses/cse331/1...
In that case, you should include CRA's config by adding this line: >```js { // . ... Some library may be incompatible with...
Read more >Frequently asked questions: Heartbleed - Canada.ca
This software is called OpenSSL. This bug has the potential to expose private data. The CRA uses OpenSSL to authenticate users of its...
Read more >CHANGELOG-1.x.md - facebook/create-react-app - Sourcegraph
#3408 Add --info flag to help gather bug reports. ... If you previously used HTTPS=true environment variable in development, make sure you aren't...
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 has been solved by adding a meta dependency on
package.json
:From: https://next.yarnpkg.com/configuration/manifest/#dependenciesMeta.unplugged
This still produces the same error for us,
yarn=2.0.0-rc.29