Technical Bug Report: EdgeParse Node.js - Windows Binary Resolution Failure
Environment
- OS: Windows 10/11 (x64)
- Node.js: v24.13.1 (or similar)
- Library Version: edgeparse@0.2.3
Issue Summary
The edgeparse Node.js package fails to load on Windows platforms because it attempts to require an optional dependency edgeparse-win32-x64-msvc which is not available in the NPM registry (404 Not Found).
Error Logs
[EDGEPARSE] Error al procesar PDF: Error: Cannot find module 'edgeparse-win32-x64-msvc'
Require stack:
- C:\...\node_modules\edgeparse\dist\index.js
at node:internal/modules/cjs/loader:1448:15
...
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\\...\\node_modules\\edgeparse\\dist\\index.js'
]
Technical Observations
- In
package.json, the library defines edgeparse-win32-x64-msvc as an optionalDependency.
- Running
npm install edgeparse-win32-x64-msvc returns a 404 Not Found from the NPM registry, indicating the package was never published or is private.
- Although the
.node binary exists physically inside the node_modules/edgeparse/npm/win32-x64-msvc/ folder after the main install, the internal logic in dist/index.js (line 36: return require(pkg);) expects it to be a resolvable module in node_modules.
Proposed Fix
The author should either:
- Publish the missing sub-packages to NPM.
- Or update
loadNative() to fall back to the local npm/ directory bundled within the main package if the module requirement fails.
Technical Bug Report: EdgeParse Node.js - Windows Binary Resolution Failure
Environment
Issue Summary
The
edgeparseNode.js package fails to load on Windows platforms because it attempts to require an optional dependencyedgeparse-win32-x64-msvcwhich is not available in the NPM registry (404 Not Found).Error Logs
Technical Observations
package.json, the library definesedgeparse-win32-x64-msvcas anoptionalDependency.npm install edgeparse-win32-x64-msvcreturns a 404 Not Found from the NPM registry, indicating the package was never published or is private..nodebinary exists physically inside thenode_modules/edgeparse/npm/win32-x64-msvc/folder after the main install, the internal logic indist/index.js(line 36:return require(pkg);) expects it to be a resolvable module innode_modules.Proposed Fix
The author should either:
loadNative()to fall back to the localnpm/directory bundled within the main package if the module requirement fails.