Remove loose-envify dep and browserify configs

[gaearon]

Browserify isn't widely used, and at this point I don't think it makes sense to have a special config just for the sake of it. Let's remove it?

[react-sizebot]

Comparing: 5f2c6b7...0e384f6

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js	=	176.93 kB	176.93 kB	=	55.14 kB	55.14 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js	=	179.07 kB	179.07 kB	=	55.82 kB	55.82 kB
facebook-www/ReactDOM-prod.classic.js	=	594.04 kB	594.04 kB	=	104.94 kB	104.94 kB
facebook-www/ReactDOM-prod.modern.js	=	577.32 kB	577.32 kB	=	101.96 kB	101.96 kB
test_utils/ReactAllWarnings.js	Deleted	66.40 kB	0.00 kB	Deleted	16.26 kB	0.00 kB

Significant size changes

Includes any change greater than 0.2%:

Expand to show

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
test_utils/ReactAllWarnings.js	Deleted	66.40 kB	0.00 kB	Deleted	16.26 kB	0.00 kB

Generated by 🚫 dangerJS against 0e384f6

[rickhanlonii]

@gaearon should we remove /fixtures/browserify too?

[gaearon]

@gaearon should we remove /fixtures/browserify too?

Maybe worth updating to whatever the alternative pattern is (when the package doesn't include the transform). Or, if we're deleting it, we might as well delete the whole folder because all other solutions there (like systemjs or rjs) are also very old and are not widely used anymore.

[ljharb]

this does constitute a breaking change, tho, i think?

[gaearon]

Yea but the next semver release we're doing will be a major. As for canaries, those may contain breaking changes as usual — so people using canaries should pin their versions.