aws-powertools/powertools-lambda-typescript

Bug: @aws-lambda-powertools/commons is not declared in batch package

Closed this issue · 3 comments

Grmiade commented

Expected Behavior

Should be able to resolve @aws-lambda-powertools/commons/utils/env in the batch package.

Current Behavior

✘ [ERROR] Could not resolve "@aws-lambda-powertools/commons/utils/env"

node_modules/.pnpm/@aws-lambda-powertools+batch@2.26.0/node_modules/@aws-lambda-powertools/batch/lib/esm/BasePartialBatchProcessor.js:1:33:
1 │ ...getStringFromEnv } from '@aws-lambda-powertools/commons/utils/env';

Code snippet

N/A

Steps to Reproduce

  1. Upgrade to 2.26.0
  2. Try to bundle this version with esbuild

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

latest

AWS Lambda function runtime

22.x

Packaging format used

npm

Execution logs

boring-cyborg commented 
Thanks for opening your first issue here! We'll come back to you as soon as we can.

In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link
dreamorosi commented 
Hi @Grmiade, thank you for reporting this and for opening a pull request to fix it.


The bug is valid and we'll be making a patch release later this morning with the fix.


We'll also be looking at improvements in our test suite to catch this type of error earlier.
  • 👍1
powertools-for-aws-oss-automation commented 
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either reopen the issue, or open a new issue referencing this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.