Break out ndb-inspect as a npm package
See original GitHub issueThe current repo has an embedded npm package ndb-inspect
. Evidently the only source for this package is here inside of this project. This awkward arrangement confuses the folks who review our use of npm modules.
I think the system would be clearer if we went one of two directions:
- spin out ndb-inspect as its own project.
- remove the npm trappings and just load the js where needed.
Would a Pull Request along one of these lines be considered?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Using npm packages in your projects
If you are creating a Node.js module, you can use a package in your module by passing it as an argument to the...
Read more >package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >Downloading and installing packages locally - npm Docs
This is npm install 's default behavior. Installing an unscoped package. Unscoped packages are always public, which means they can be searched for,...
Read more >npm-install - npm Docs
Description. This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap...
Read more >About packages and modules - npm Docs
The npm registry contains packages, many of which are also Node modules, ... A package is a file or directory that is described...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Latest ndb@1.0.33 contains fix for ndb/inspect-brk. Thanks for your bug report.
Unfortunately in Node.js it is not possible to require globally installed module. It might be possible only with extending NODE_PATH environment variable [1]. [1] https://stackoverflow.com/questions/15636367/nodejs-require-a-global-module-package