chore(maintenance): move dev tooling to devDependencies in private workspaces - #5595
Merged
Conversation
dreamorosi
reviewed
Aug 30, 2026
dreamorosi
approved these changes
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
A couple of private workspaces declared build/test tooling (
esbuild,typescript,@types/*) underdependenciesinstead ofdevDependencies. Dependabot classifies updates as production or development based on where a package is declared across the repo, so these misplacements caused routine tooling bumps to be labelled as production dependencies and excluded from the dev-dependency auto-merge workflow. Both workspaces are private and never published to npm, so the change has no effect on anything we ship.Changes
examples/app: remove@types/node,@types/aws-lambda, andtypescriptfromdependencies(they were already duplicated indevDependencies), and moveesbuildtodevDependencieslayers: moveesbuildtodevDependenciespackage-lock.jsonso the workspace declarations anddevflags reflect the moves; all resolved versions stay at main's pinspackages/testingkeepsesbuildas a production dependency — it backs theNodejsFunctionL3 construct the package provides, so it's production as far as this package is concerned (see review discussion).Issue number: closes #5593
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.