feat!: remove process global to work outside of node

[styfle]

In order to support more JS runtimes besides Node.js, this PR drops the check for process global.

The process global was only used to improve the error message for Node.js less than 10 (released April 2018).

This could be considered a breaking change since the error message will change, however this package already specifies package.json engines.node with >=10, so perhaps no one can even run it on older versions of Node.js without an install error.

picomatch/package.json

Line 20 in 5214db4

"node": ">=10"

• Related to Browser compatibility #123

[coveralls]

coverage: 92.382% (+0.03%) from 92.355%
when pulling 3b2726c on styfle:remove-process-global
into 5214db4 on micromatch:master.

[styfle]

I realize now that typeof process !== 'undefined' should have caught this 🤦‍♂️

My use case is actually babel attempting to read process as seen in vercel/next.js#61116

I think this PR is still useful though since the default value assumed false for non-Node.js runtimes and my PR assumes true 😃

[jonschlinkert]

@styfle thanks for the PR. I agree with all of your points. I'll get this merged in an probably publish a major asap. Thanks!

[styfle]

@jonschlinkert Thanks for the quick response! 🎉

[jonschlinkert]

Done, I just published v4.0.

If anyone wants to do a PR in micromatch to upgrade picomatch to latest, I'd be happy to accept.

[styfle]

Great! I created a micromatch PR here:

• chore!: bump picomatch@4.0.1 micromatch#248