Skip to content

Docs: add info on how to package utilities #1525

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
dreamorosi opened this issue Jun 20, 2023 · 1 comment · Fixed by #1526
Closed
1 task done

Docs: add info on how to package utilities #1525

dreamorosi opened this issue Jun 20, 2023 · 1 comment · Fixed by #1526
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation

Comments

@dreamorosi
Copy link
Contributor

What were you searching in the docs?

Note
This issue has been opened in response to the discussion opened by @brianhyder

Some customers might need/want to package one or more utility instead of using the version published on npm. This is useful both during development and testing, as well as when needing to install a nightly version that hasn't been published.

Is this related to an existing documentation section?

No response

How can we improve?

We should provide instructions on how to build one or more packages in the `CONTRIBUTING` docs.

Got a suggestion in mind?

No response

Acknowledgment

  • I understand the final update might be different from my proposed suggestion, or refused.
@dreamorosi dreamorosi added documentation Improvements or additions to documentation confirmed The scope is clear, ready for implementation labels Jun 20, 2023
@dreamorosi dreamorosi self-assigned this Jun 20, 2023
@dreamorosi dreamorosi linked a pull request Jun 20, 2023 that will close this issue
docs: refresh contributing docs #1526
Merged
9 tasks
@dreamorosi dreamorosi mentioned this issue Jun 20, 2023
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Jun 20, 2023
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

@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 Jun 20, 2023
@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 Jun 20, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs: refresh contributing docs aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi