yodaos-project/ShadowNode

module: optional `.node` extension

Open

#265 opened on Aug 8, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (588 stars) (45 forks)batch import
good first issuemodule

Description

  • Version: 0.9.0
  • Platform: all
  • Subsystem: module

require('build/binding') could be used to load build/binding.node in node.js, which shall be supported in ShadowNode for compatibility.

Contributor guide

Tech stack
javascript
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js module resolutionShadowNode module system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the module resolution logic in ShadowNode, likely in the JavaScript or C++ source. Look for how require resolves file extensions. The issue references node.js behavior where require('build/binding') loads build/binding.node. Examine the existing extension resolution (e.g., .js, .json) and add support for .node as an implicit extension when the module name has no extension. Check if there is any existing handling for .node files in the source code, such as in module.js or native addon loading code.