fix(devtools): include infrastructure/ in npm package files #519
Conversation
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
The doctor-command requires files from infrastructure/domains/health/ but the infrastructure/ directory was not included in the package.json files array. This caused deployments to fail with: Error: Cannot find module '../../infrastructure/domains/health/domain/value-objects/stack-identifier' Add infrastructure/ to the files array to ensure it's published to npm.
|
seanspeaks
approved these changes
Dec 15, 2025
d-klotz
deleted the
fix/include-infrastructure-in-devtools-npm-package
branch
4 tasks
Contributor
|
🚀 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
infrastructure/to thefilesarray in devtoolspackage.jsonProblem
The
doctor-commandrequires files frominfrastructure/domains/health/but theinfrastructure/directory was not included in the npm package. This caused deployments to fail with:Solution
Add
infrastructure/to thefilesarray inpackages/devtools/package.jsonto ensure it's published to npm.Version
Published prerelease version:
v2.0.0-next.63Changelog
🐛 Bug Fix
@friggframework/devtools@friggframework/core,@friggframework/devtools,@friggframework/eslint-config,@friggframework/prettier-config,@friggframework/schemas,@friggframework/serverless-plugin,@friggframework/test,@friggframework/uiAuthors: 3