Is your proposal related to a problem?
Not really related to a problem. In the last couple of months I have found myself in a situation where I was really interested in testing something that was merged in the master branch, but not yet released. Happened to me now with the experimental support for fast refresh, also happened in the past with the support for TS3.7 and the ability to change webpack dev server host/port
Describe the solution you'd like
Some other libs in the community do alpha/beta or nightly releases to allow developers to play with the latest things merged to master. I created this issue after discussing this with @mrmckeb in spectrum
Describe alternatives you've considered
An easy alternative is to clone create-react-app and link react-scripts locally... but this process does not really scale when working with several developers in the same repo and all of them have to do the same on their own.
Other alternative was to try to build react-scrips locally and publish it github packages, then all my colleagues could just install that dependency from that registry instead... but being honest I couldn't make that work.
The same for trying to publish react-scripts to npm registry changing the name to something like @sbalay/react-scripts
Additional context
I think that I'm not the only one interested in this, several people in the community follow the excellent work that you do in this repo day to day and are eager to test things and help out 🙂
Is your proposal related to a problem?
Not really related to a problem. In the last couple of months I have found myself in a situation where I was really interested in testing something that was merged in the master branch, but not yet released. Happened to me now with the experimental support for fast refresh, also happened in the past with the support for TS3.7 and the ability to change webpack dev server host/port
Describe the solution you'd like
Some other libs in the community do alpha/beta or nightly releases to allow developers to play with the latest things merged to master. I created this issue after discussing this with @mrmckeb in spectrum
Describe alternatives you've considered
An easy alternative is to clone create-react-app and link react-scripts locally... but this process does not really scale when working with several developers in the same repo and all of them have to do the same on their own.
Other alternative was to try to build react-scrips locally and publish it github packages, then all my colleagues could just install that dependency from that registry instead... but being honest I couldn't make that work.
The same for trying to publish react-scripts to npm registry changing the name to something like @sbalay/react-scripts
Additional context
I think that I'm not the only one interested in this, several people in the community follow the excellent work that you do in this repo day to day and are eager to test things and help out 🙂