Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Alternative build tool for @appsignal/nodejs-ext #16

Closed
adamyeats opened this issue Dec 19, 2019 · 2 comments
Closed

Alternative build tool for @appsignal/nodejs-ext #16

adamyeats opened this issue Dec 19, 2019 · 2 comments
Assignees
@adamyeats
Labels
enhancement

Comments

@adamyeats
Copy link
Contributor

Hearing online that there may be better solutions out there than node-gyp. One example is CMake.js. Another is Bazel, but this seems way too complex for our use case.

gyp is not actively maintained and depends on Python 2.7, which is not great in an (finally) increasingly Python 3 world.

See #13 for another issue with node-gyp.
@adamyeats adamyeats self-assigned this Dec 19, 2019
@adamyeats adamyeats transferred this issue from another repository Feb 1, 2020
@backlog-helper
Copy link

backlog-helper bot commented Feb 1, 2020 •
edited
Loading

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

@adamyeats adamyeats changed the title Alternative build tool for native extensions Alternative build tool for @appsignal/nodejs-ext Apr 24, 2020
@adamyeats
Copy link
Contributor Author

Closing this as node-gyp seems like it will remain the best option for the time being. cmake-js requires a custom buildpack on Heroku, which would degrade the user experience for customers on Heroku.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adamyeats adamyeats

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tombruijn @adamyeats