This repository was archived by the owner on May 10, 2021. It is now read-only.
This repository was archived by the owner on May 10, 2021. It is now read-only.
Closed
Description
stakeholders: @FinnWoelm @ehmicky
This issue is to publicly discuss an internal discussion around inlining next-aws-lambda.
Original issues with depending on next-aws-lambda:
- plugin dependency issue (Remove
npm install next-on-netlifyopennextjs/opennextjs-netlify#10) (this is being addressed internally) - miscellaneous user-reported issues
To move forward and relieve some tension with these open issues, we've temporarily inlined next-aws-lambda with Finn's awesome PR. However, @ehmicky brought up concerns around future maintenance issues with inlining.
Options:
- Inline the package (most fine-grained control but needing to repeatedly update a semi-active project)
- Use patch-package
- Fork the project (monorepo though)
- Open PRs upstream (this could benefit both the greater Next.js community and other Netlify plugins)
While we all agree inlining is a great first step and improvement from what we had for the original issues, let's try to align on the best path forward.
Metadata
Metadata
Assignees
Labels
No labels