Strange behavior with my pre-build module when downloading from remote
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
I have a module called `node-libxml` coming from https://github.com/jupitex/node-libxml (up-to-date on master)
I recently worked on a V4.0.0 converted to n-api from nan , when I install `npm i node-libxml` it create a file instead of a folder `build/Release/7` with the n-api version instead of `build/Release/7/xml.node`
I check everywhere but do not understand what am I missing 🧐
Futhermore with a dynamic path as `build/Release/7/xml.node`, `build/Release/6/xml.node`.. how am I suppose to load it ?
Thanks for all advice Mapbox team 👌
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.
Research direction
Reproduce the remote install with `npm i node-libxml` and inspect the reported `build/Release/7` path, comparing it with the expected `build/Release/7/xml.node` and other ABI paths. Determine whether the generated layout and dynamic loading behavior are intended, and document or verify the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100