-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationnot-a-bugNew and existing bug reports incorrectly submitted as bugNew and existing bug reports incorrectly submitted as bugrejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future
Milestone
Description
Bug description
Reported by @michaelbrewer on the Slack Dev channel.
Unable to install package after clean clone of repo, see screenshot above.
Expected Behavior
Be able to git clone ...
& npm install
.
Current Behavior
Throws an error for missing import of @aws-lambda-powertools/commons
(see screenshot).
Possible Solution
N/A
Steps to Reproduce
git clone
npm i
Environment
- Powertools version used: 0.2.0
- Packaging format (Layers, npm): npm
- AWS Lambda function runtime: N/A - local development
- Debugging logs:
npm --version
8.3.0
node --version
17.3.0
Running on Apple Silicon
Related issues, RFCs
N/A
michaelbrewer
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationnot-a-bugNew and existing bug reports incorrectly submitted as bugNew and existing bug reports incorrectly submitted as bugrejectedThis is something we will not be working on. At least, not in the measurable futureThis is something we will not be working on. At least, not in the measurable future