Accessing `module.id` breaks
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
Log from the UI https://zeit.co/olstenlarck/tunnckocore-release-now-v2/agkrauawz
Error while initializing entrypoint: TypeError: u.startsWith is not a function
at Object.<anonymous> (/var/task/user/index.js:152:281)
at Object.<anonymous> (/var/task/user/index.js:153:30)
at __webpack_require__ (/var/task/user/index.js:21:30)
at Object.<anonymous> (/var/task/user/index.js:130:19)
at Object.<anonymous> (/var/task/user/index.js:146:30)
at __webpack_require__ (/var/task/user/index.js:21:30)
at module.exports.module.exports.module.deprecate (/var/task/user/index.js:85:18)
at Object.<anonymous> (/var/task/user/index.js:88:10)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the linked UI log and the generated /var/task/user/index.js stack, then trace how the module.id access reaches ncc's entrypoint handling. The report does not name a repository file or test; completion should include a reproducible case where accessing module.id no longer triggers the shown TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100