Logger updates: dependencies and higher minimum node version #1650
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is mainly intended as a discussion point.
I would like to do some updates in this repository. Recently the build for this repo was broken and this prompted me to look into it more. There are many issues with this repo, but I'd like to slowly chip away at improving things.
This PR is a template for what I would like to roll out to all the other non-deprecated packages in this repo. In short:
I wanted to see what the team thinks of these changes? What are your opinions? Do you agree or disagree with any of these changes, in particular the raising of the minimum node version? And do you think this should warrant a major semver version increase?
Longer term, after these initial updates I would also like to tackle:
package.json
. Possibly this could leverage npm workspaces, though my initial foray into this area was unsuccessful, but I think mostly due to trying to support too many incompatible node versions at the same time.