npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-calls-python-embedded

v0.0.13

Published

Modification of the node-calls-python module, allowing you to run an embedded python interpreter within node.

Downloads

41

Readme

node-calls-python-embedded - call an embedded Python interpreter from Node.js directly in-process without spawning processes

modification of the "node-calls-python" module

Common Issues

Node-Gyp Issues

When re-building the node-calls-python module (after modifications), the following error:

LINK : fatal error LNK1181: cannot open input file 'Cannot find PYTHON.lib' [C:\Users\toby\Documents\Sonobotics\Sonobot
ics-App\node_modules\node-calls-python\build\nodecallspython.vcxproj]

Usually means that the pythonXX\Scripts\ directory (of the python development instance) has not been added to the path.

DLL issues

When facing an electron error like this (after calling npm start):

Error: The specified module could not be found.
\\?\C:\Users\toby\Documents\Sonobotics\Sonobotics-App\node_modules\node-calls-python\build\Release\nodecallspython.node
    at process.func [as dlopen] (node:electron/js2c/node_init:2:2559)
    at Module._extensions..node (node:internal/modules/cjs/loader:1470:18)
    at Object.func [as .node] (node:electron/js2c/node_init:2:2559)
    at Module.load (node:internal/modules/cjs/loader:1215:32)
    at Module._load (node:internal/modules/cjs/loader:1031:12)
    at c._load (node:electron/js2c/node_init:2:17025)
    at Module.require (node:internal/modules/cjs/loader:1240:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> 

It usually means that the "node-calls-python" module cannot find the pythonXX.DLL file.
Make sure this file is added to node-calls-pytho\build\Release as the nodecallspython.node file will immediately look for dependencies in this location. The difficulty is that this directory is wiped every time the module is recompiled. Alternatively, adding it to the root sonobotics-app directory seems to work too. In the packaged app we want this file next to the .exe, so we use the "extraResources" term in the package.json file to move it there when packaging