-
Notifications
You must be signed in to change notification settings - Fork 123
review dependencies #3771
Comments
Here's the always mildly-suspicious output from depcheck: ➜ testpilot git:(master) $ git rev-parse --short HEAD # a8682f5b
➜ testpilot git:(master) $ npx depcheck@latest
Unused dependencies
* domready
* legal-docs
Unused devDependencies
* autoprefixer
* babel-eslint
* babel-register
* cross-spawn
* cssnano
* empty
* eslint-config-react
* eslint-plugin-jsx-a11y
* flow-typed
* gulp-cache
* gulp-if
* gulp-multi-dest
* gulp-rename
* gulp-uglify
* merge-stream
* mocha-junit-reporter
* node-normalize-scss
* photon-colors
* react-addons-test-utils
* react-test-renderer
* require-globify
* url-loader
* vinyl-source-stream
Missing dependencies
* eslint-config-plugin:import
* eslint-config-plugin:flowtype
* eslint-config-plugin:react
* eslint-config-plugin:mozilla
* @storybook/addon-links
* globby
* l20n
* redux-actions
* isomorphic-fetch
* react-router-redux
* history
* redux-logger
* redux-thunk
* fbjs
* object-assign
* _process
* select
* lodash.isplainobject
* delegate
* warning
* invariant
* deep-equal
* query-string
* lodash._basefor
* lodash.isarguments
* lodash.keysin
* lodash.isarray
* strict-uri-encode
* json-stringify-safe
* lodash
* hoist-non-react-statics
* reduce-reducers
* deep-diff
* symbol-observable
* tiny-emitter
* good-listener
* flux-standard-action |
Here is output for
11 of our deps are in the red AddonAll of our addon dependencies are needed at the moment. All of them are dev dependencies so we don't have the same level of security concern for these.
3 are in the red |
Been working on this for a few days now,
|
I noticed that Test Pilot uses both This might be relevant to the Fluent upgrade in #3789. Fluent's
While
PS Always bet on JavaScript. |
We're 5/7 of the way through removing Gulp from our build chain (it's been a slow process) - but we don't actually use gulp-uglify any more as far as I can tell. So, it's just uglifyjs-webpack-plugin. We can upgrade that, as long as it doesn't cause an upgrade cascade that we've been trying to avoid for the time being. Also I think the larger issue is not just whether uglify fails - but whether we want to switch from transpiled ES5 to serving up straight ES6 code, right? I'm not sure we want to do that yet. Maybe it's okay with respect to our browser support goals? I don't know off the top of my head. |
The version of
Looking at Test Pilot's FAQ, I sense some enthusiasm about shipping ES6+ code :) FWIW new releases of Fluent packages are currently targeting the following browsers with its transpiled
|
This commit was authored by meandavejustice, but there was some git weirdness, so I am helping out by squashing it into a new commit on top of master.
Have you considered using something like dependabot or greenkeeper to keep your npm dependencies up-to-date? I use dependabot and it works quite well for my projects :) |
We were using greenkeeper. But, we had a long run of it suggesting backwards-incompatible upgrades. The pull requests kind of piled up as tech debt chasing upstream API changes at a time when we were busy doing other things as a team (e.g. Test Pilot experiments). We disabled greenkeeper with the intent to get back to it (or something like it), but haven't quite done it yet. |
I tried to enable renovate today, but couldn't figure out how. Not sure if that says more about me or GitHub's app system.... :-/ |
Alright renovate is enabled! For the record: The Mozilla org had already approved Renovate for use in the org, however, a repository owner cannot turn it on. You have to be an org owner to add it to the repository... which is weird. Anyway... |
We have a lot of them! https://github.com/mozilla/testpilot/network/dependencies
The text was updated successfully, but these errors were encountered: