Skip to content

Bug: package-lock.json might have been generated with node@16 breaking node@14 user build #502

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
flochaz opened this issue Jan 24, 2022 · 3 comments
Closed

Bug: package-lock.json might have been generated with node@16 breaking node@14 user build #502

flochaz opened this issue Jan 24, 2022 · 3 comments
Assignees
@dreamorosi
Labels
dependencies Changes that touch dependencies, e.g. Dependabot, etc. not-a-bug New and existing bug reports incorrectly submitted as bug rejected This is something we will not be working on. At least, not in the measurable future
Milestone
production-ready-...

Comments

@flochaz
Copy link
Contributor

flochaz commented Jan 24, 2022 •
edited
Loading

Bug description

See #326 (comment)

Expected Behavior

TBD

Current Behavior

TBD

Possible Solution

TBD

Steps to Reproduce

TBD

Environment

  • Powertools version used: 0.4.0
  • Packaging format (Layers, npm): npm
  • Debugging logs: TBD

Related issues, RFCs

#326
#501
@flochaz flochaz added bug Something isn't working triage This item has not been triaged by a maintainer, please wait labels Jan 24, 2022
@dreamorosi
Copy link
Contributor

Were you able to reproduce? Same user who reported opened a PR which then he closed after installing [email protected] like the contributions docs say.

@flochaz
Copy link
Contributor Author

flochaz commented Jan 24, 2022

Nope, indeed. closing.

@flochaz flochaz closed this as completed Jan 24, 2022
@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.

@dreamorosi dreamorosi added rejected This is something we will not be working on. At least, not in the measurable future and removed triage This item has not been triaged by a maintainer, please wait labels Jan 24, 2022
@dreamorosi dreamorosi added this to the production-ready-release milestone Feb 28, 2022
@dreamorosi dreamorosi added not-a-bug New and existing bug reports incorrectly submitted as bug dependencies Changes that touch dependencies, e.g. Dependabot, etc. and removed bug Something isn't working labels Nov 14, 2022
@dreamorosi dreamorosi moved this from Shipped to Closed in AWS Lambda Powertools for TypeScript Nov 14, 2022
@dreamorosi dreamorosi self-assigned this Nov 14, 2022
@dreamorosi dreamorosi changed the title fix(examples): package-lock.json might have been generated with node@16 breaking node@14 user build Bug: package-lock.json might have been generated with node@16 breaking node@14 user build Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
dependencies Changes that touch dependencies, e.g. Dependabot, etc. not-a-bug New and existing bug reports incorrectly submitted as bug rejected This is something we will not be working on. At least, not in the measurable future
Projects
None yet
Milestone
production-ready-release
Development

No branches or pull requests
2 participants
@flochaz @dreamorosi