-
-
Notifications
You must be signed in to change notification settings - Fork 747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Typescript] Update dependencies #270
Comments
WIP PR #276 |
Once we have manually updated the dependencies I would be happy to implement weekly dependabot pull requests that keep all dependencies up-to-date. |
#276 was closed, the approach was bad, there is a new branch that is passing but not complete yet, identifying which libraries break where.. It was just automatically closed by merge and delete the typescript branch, so I will recreate the PR and point to main instead. For reference here is the old closed PR |
for reference new updated PR #304 pointing to main branch |
Resolves #270 * update typescript to 4.4.2 update testem to 3.5.0 update eslint update selenium (from beta.4 to rc-1) update rollup, plugin-strip and remove deprecated rolllup @types update react, react-dom and types update @babel/core to 7.15.0 update stylelint 9.10.1 -> 13.13.1, types and config patch update to @types/jsonwebtoken patch update to @types/request update tape to 5.3.1 update sinon to 11.1.2 and types update semver to 7.3.5 update chalk to 4.1.2 update browserify to 17.0.0 update cssnano to 5.0.8 update pngjs to 6.0.0 and types update patch @babel/core 7.15.4 update puppeteer to 10.2.0 update json-stringify-pretty-compact to 3.0.0 update ejs to 3.1.6 and types update st to 3.0.0 * update nyc to 15.1.0 * update @octokit/rest to 18.10.0 * update node-notifier to 10.0.0 * update npm-packlist to 3.0.0 * update @mapbox/mapbox-gl-supported to 2.0.0 * update @mapbox/gazetteer to 5.1.0
In order to make sure this library is up-to-date we should upgrade dependencies once the typescript branch makes its way to main in order to make sure we don't have any security issues and deprecation stuff.
The text was updated successfully, but these errors were encountered: