Including node_modules in the minification
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, javascript, node.js
- Domain
- build-system, cloud
Research direction
Reproduce the build command using the layout shown in the errors, especially src//node_modules and yarn.lock. Determine why those paths are included in minification, then verify that the resulting Lambda@Edge viewer-request bundle excludes unnecessary files and remains under the 1 MB limit.
Written by the indexing model from the issue text.
Description
Hello. Thanks for sharing this sample project.
I came from this article and need to use my code for a Lambda@Edge (viewer-request), limited to 1MB size.
When I try to run the build command, I got these issue:
✘ [ERROR] Could not resolve "./src/<function-name>/node_modules"
✘ [ERROR] No loader is configured for ".lock" files: src/<function-name>/yarn.lock
If you can help out, I would really appreciate it!
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·