Maintenance: add biome to project (tracer) #2803
Assignees
Labels
automation
This item relates to automation
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.)
tracer
This item relates to the Tracer Utility
Comments
dreamorosi
added
automation
github-project-automation
bot
moved this to Triage
in Powertools for AWS Lambda (TypeScript)
dreamorosi
moved this from Backlog
to Working on it
in Powertools for AWS Lambda (TypeScript)
This was referenced Jul 22, 2024
dreamorosi
moved this from Working on it
to Pending review
in Powertools for AWS Lambda (TypeScript)
github-project-automation
bot
moved this from Pending review
to Coming soon
in Powertools for AWS Lambda (TypeScript)
|
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. |
github-actions
bot
added
pending-release
|
This is now released under v2.6.0 version! |
github-actions
bot
added
completed
dreamorosi
moved this from Coming soon
to Shipped
in Powertools for AWS Lambda (TypeScript)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
With #2791 being merged, we can now migrate the
packages/tracerworkspace to use Biome.As part of the migration I will fix any issue/inconsistency that arises. I'll do my best to minimize changes and leave the logic untouched.
Why is this needed?
So that we can gradually replace
eslint,prettier, and all their dependencies with a single one,@biomejs/biome.Which area does this relate to?
Other
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: