Skip to content

Maintenance: add subpath exports to package.json #2177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 2 tasks
am29d opened this issue Mar 7, 2024 · 2 comments · Fixed by #2179
Closed
1 of 2 tasks

Maintenance: add subpath exports to package.json #2177

am29d opened this issue Mar 7, 2024 · 2 comments · Fixed by #2179
Assignees
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) parser This item relates to the Parser Utility

Comments

@am29d
Copy link
Contributor

am29d commented Mar 7, 2024

Summary

We currently don't export subpaths for envelopes, schemas and types in our package.json, and we should add them, so customers can import them.

Why is this needed?

So customers can granularly import schemas and envelopes following the same standard that we have introduced with in v2.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.

@am29d am29d added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Mar 7, 2024
@am29d am29d added this to the Parser - Beta Release milestone Mar 7, 2024
@am29d am29d self-assigned this Mar 7, 2024
@am29d am29d added parser This item relates to the Parser Utility completed This item is complete and has been merged/shipped and removed triage This item has not been triaged by a maintainer, please wait labels Mar 7, 2024
@dreamorosi dreamorosi moved this from Triage to Backlog in Powertools for AWS Lambda (TypeScript) Mar 7, 2024
@dreamorosi dreamorosi linked a pull request Mar 8, 2024 that will close this issue
9 tasks
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation and removed completed This item is complete and has been merged/shipped labels Mar 8, 2024
@dreamorosi dreamorosi moved this from Backlog to Pending review in Powertools for AWS Lambda (TypeScript) Mar 8, 2024
@dreamorosi dreamorosi moved this from Pending review to Working on it in Powertools for AWS Lambda (TypeScript) Mar 8, 2024
@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Mar 11, 2024
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Mar 11, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Mar 11, 2024
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Mar 11, 2024
Copy link
Contributor

⚠️ COMMENT VISIBILITY 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 tag a team member or open a new issue that references this one.

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

@dreamorosi
Copy link
Contributor

This is now released under v2.1.0 version!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) parser This item relates to the Parser Utility
Projects
2 participants