max-mapper / max-mapper/requirebin

requiring node core modules fails

Open
#72 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
389
Forks
73
PR merge metrics
No merged PRs in 30d

Description

This

var http = require('http')

gives

Bundling error: 

---FLAGRANT SYSTEM ERROR---

--- error #0: ---


(logs uuid: 0daef330-c86c-11e4-9de9-59ad9188bc13 )

Error: "spawn ENOENT"

code: ENOENT
errno: ENOENT
syscall: spawn
dirPath: /tmp/http115212-24815-1xspa4h


------

This is probably an issue with the package, and not browserify-cdn itself.
If you feel differently, feel free to file a bug report at:

    https://github.com/jesusabdullah/browserify-cdn/issues

Include the ENTIRETY of the contents of this message, and he can
try to help you out.

Have a nice day!

and this

var events = require('events')

gives

Bundling error: 

---FLAGRANT SYSTEM ERROR---

--- error #0: ---


(logs uuid: 3b55a810-c86c-11e4-9de9-59ad9188bc13 )

Error: "spawn ENOENT"

code: ENOENT
errno: ENOENT
syscall: spawn
dirPath: /tmp/events115212-24815-qtxstm


------

This is probably an issue with the package, and not browserify-cdn itself.
If you feel differently, feel free to file a bug report at:

    https://github.com/jesusabdullah/browserify-cdn/issues

Include the ENTIRETY of the contents of this message, and he can
try to help you out.

Have a nice day!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failures for require('http') and require('events') and trace the bundling path that reports spawn ENOENT. Check what handling exists for Node core modules; done means both examples bundle without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.