cypress-browserify-preprocessor

cypress-browserify-preprocessor copied to clipboard

This is more of just a general request to update your dependencies (see #63).

I'm getting a bunch of installation warnings all coming from packages that you depend on (that, in turn, depend on other deprecated packages).

For example, chokidar@v2 shows a deprecation warning:

➤ YN0061: │ chokidar@npm:2.1.8 is deprecated: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.

And it's used by two of your dependencies:

   ├─ @cypress/code-coverage@npm:3.9.4 [b17e5] (via npm:^3.9.4 [b17e5])
   │  └─ @cypress/browserify-preprocessor@npm:3.0.1 (via npm:3.0.1)
   │     ├─ babel-plugin-add-module-exports@npm:1.0.2 (via npm:1.0.2)
   │     │  └─ chokidar@npm:2.1.8 (via npm:^2.0.4)
   │     └─ watchify@npm:3.11.1 (via npm:3.11.1)
   │        └─ chokidar@npm:2.1.8 (via npm:^2.1.1)

Same thing with fsevents@v1:

➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

And it's also used by your dependencies:

   ├─ @cypress/code-coverage@npm:3.9.4 [b17e5] (via npm:^3.9.4 [b17e5])
   │  └─ @cypress/browserify-preprocessor@npm:3.0.1 (via npm:3.0.1)
   │     ├─ babel-plugin-add-module-exports@npm:1.0.2 (via npm:1.0.2)
   │     │  └─ chokidar@npm:2.1.8 (via npm:^2.0.4)
   │     │     └─ fsevents@patch:fsevents@npm%3A1.2.13#builtin<compat/fsevents>::version=1.2.13&hash=11e9ea (via patch:fsevents@^1.2.7#builtin<compat/fsevents>)

We're open to pull requests to update the dependencies with the appropriate changes needed from each deps changelog.