Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Build Debug Bindings for NPM

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, node.js

Research direction

Start with scripts/install-deps.sh, especially the linked lines that strip debug symbols, and inspect the existing Travis build configuration. Trace how node-pre-gyp packages the current binaries, then determine how a --debug build would be published and released. Done means debug binaries are built without stripped symbols, published, included in a new release, and visible in S3.

Written by the indexing model from the issue text.

Description

enhancement

In https://github.com/mapbox/node-or-tools/pull/23 we switched to statically linking against upstream libortools.a and more importantly strip out debug symbols here. What we should do is build debug binaries for npm which link against libortools.a with debug symbols not stripped out.

Tasks:

  • Create Travis builds for debug binaries which do not strip out debug symbols
  • Publish debug binaries passing --debug to node-pre-gyp
  • Make a new release https://github.com/mapbox/node-or-tools#releases
  • Check s3 to see if debug binaries are there

cc @karenzshea

Dominant language
C++
Stars
155
Forks
47
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from mapbox/node-or-tools

All issues in mapbox/node-or-tools

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.