chore: move TypeScript type dependencies to dev dependencies

[fxOne]

What/Why/How?

Currently, @types/node is a dependency in the @redocly/openapi-core package. As these are only TypeScript types, they are not needed in production and can be moved to a dev dependency.

Also, there is already a @types/node@17.0.31 in the root package. My question would be whether the dependency there should be sufficient and whether the dependency should be changed to a more up-to-date version.

Reference

Testing

Screenshots (optional)

Check yourself

• Code is linted
• Tested with redoc/reference-docs/workflows (internal)
• All new/updated code is covered with tests

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: eda23fb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[tatomyr]

Thank you for spotting this on!
You absolutely can try updating the types to a newer version unless there're massive issues with that.

[lornajane]

@tatomyr Do we need to wait for the types dependency to be updated, or would this pull request be useful as it is?

[tatomyr]

@lornajane no we don't. If @fxOne won't update this, I'll merge this MR as it is before the next release.

[fxOne]

@tatomyr I have updated @types/node to the latest version.

[tatomyr]

Thank you @fxOne for improving Redocly CLI! 😄