upgrade dependencies to reduce deprecation warnings - #5043
Conversation
| "form-data": "^4.0.4", | ||
| "mocha": "^10.7.3", | ||
| "nyc": "^15.1.0", | ||
| "replace-in-file": "^6.1.0", |
| "devDependencies": { | ||
| "eslint-config-apostrophe": "^5.0.0", | ||
| "eslint": "^9.34.0", | ||
| "eslint-config-apostrophe": "github:apostrophecms/eslint-config-apostrophe#pro-8109-upgrade-dependencies", |
There was a problem hiding this comment.
TODO: use version 6 when apostrophecms/eslint-config-apostrophe#22 is merged
| "tough-cookie": "^4.0.0", | ||
| "underscore.string": "^3.3.4", | ||
| "uploadfs": "^1.24.3", | ||
| "uploadfs": "github:apostrophecms/uploadfs#pro-8109-upgrade-dependencies", |
There was a problem hiding this comment.
TODO: use version 6 when apostrophecms/uploadfs#103 is merged
There was a problem hiding this comment.
I think you meant to say we can go back to depending on npm after uploadfs is published. And that it will use gcs 7, not 6.
Flagging we have to do this before publishing.
There was a problem hiding this comment.
exactly, sorry,
TODO: use version 1.25.1*
There was a problem hiding this comment.
Unused file that included replace-in-file dependency, which was not used either in this file
| globalIgnores([ | ||
| '**/vendor/**/*.js', | ||
| '**/blueimp/**/*.js', | ||
| '**/node_modules', | ||
| 'test/public', | ||
| 'test/apos-build', | ||
| 'coverage' | ||
| ]), |
There was a problem hiding this comment.
This is the way to ignore files now... https://eslint.org/docs/latest/use/configure/ignore
There was a problem hiding this comment.
Ok, but why having it at project level and not in the global config?
My take is that we shouldn't introduce project level configuration. We already spent time refactoring this and it might make future migration to monorepos easier.
There was a problem hiding this comment.
I only moved these from the deleted .gitignore file: https://github.com/apostrophecms/apostrophe/pull/5043/files#diff-a0fdacd2ade87c5238dde44378f574f7e123e669acdf8b740878b14b33b20275
I suggest we'll do this work in a separate PRs in order to scope that
There was a problem hiding this comment.
I have added data and apos-build to the globalIgnore in eslint-config-apostrophe
ValJed
left a comment
There was a problem hiding this comment.
Should not have removed rules like max-len.
| globalIgnores([ | ||
| '**/vendor/**/*.js', | ||
| '**/blueimp/**/*.js', | ||
| '**/node_modules', | ||
| 'test/public', | ||
| 'test/apos-build', | ||
| 'coverage' | ||
| ]), |
There was a problem hiding this comment.
Ok, but why having it at project level and not in the global config?
My take is that we shouldn't introduce project level configuration. We already spent time refactoring this and it might make future migration to monorepos easier.


Summary
Following deprecation warnings fixed ✅ :
eslint(viaeslint-config-apostrophe)@humanwhocodes/object-schemagoogle-p12-pem(viauploadfs)Couldn't fix these ❌ :
inflight: brought byglobvianycat its most up to date version:Note that upgrading mocha did reduce the usage of
inflightbecause latest version is usingglob10.glob7: still too widely used by other dependenciesrimraf3: still used bynycat its latest versionquerystring: brought byaws-sdkat its most up to date version:beforeafterWhat are the specific steps to test this change?
For example:
What kind of change does this PR introduce?
(Check at least one)
Make sure the PR fulfills these requirements:
If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.
Other information: