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

@phoenix-plugin-registry/brackets-nodejs-integration

v1.8.17

Published

Use 'brackets-npm-registry' to install. NodeJS integration is Nodejs, mocha, npm and gulp runner with interactive debugger and RequireJS improvements.

Downloads

3

Readme

Brackets - NodeJS integration

GitHub stars GitHub forks GitHub license GitHub issues

Brackets - NodeJS integration is an extension for Brackets editor - it provides Nodejs and Mocha integration for Brackets. It's tested and works on any platform supported by Brackets (Windows, Mac OS X, GNU/Linux).

Installation

Dependencies:

To make Brackets - NodeJS integration work you'll need nodejs, npm and mocha installed in your system:

Extension installation:

Use brackets-npm-registry

Configuration:

Extension can be configured by opening the NodeJS integration Panel and clicking the Open settings button.

Features and limitations

Currently Brackets - NodeJS integration supports these features (this list may be incomplete as we add new features regularly):

  • Run multiple nodejs processes inside editor with console output (actual limit is only 5 processes, because brackets connections limitation)
  • Run current NodeJS file (Ctrl-Shift-N)
  • Run current NodeJS project (Ctrl-Shift-P)
  • Run current Mocha test (Ctrl-Shift-T)
  • Run npm scripts
  • Run gulp scripts
  • Run mocha test inside editor with tree view results
  • Open file via mouse click from error stack
  • Show Actual/Expected difference for mocha test
  • Double click on mocha test case to open file with it
  • Jump to require command uses "Jump to declaration" and opens required file (Ctrl-Shift-J or Cmd-Shift-J)
  • Code hints for require: actual directory content, NodeJS built-in libs and project packages from package.json (use Ctrl-Space or Cmd-Space while require)
  • NodeJS and Mocha debugger integration (based on TheBenji work)

Some screenshots:

main
Main panel of NodeJS integration - run nodejs process

mocha
Main panel of NodeJS integration - run mocha test

goto_error
Main panel of NodeJS integration - quick open error file

require_hints
RequireJS - Show hints while require

asert_diff
Mocha test result - Show asert difference

settings
Settings dialog

How to use debugger

  • Start your script in debug mode
  • Use the Buttons to Step over, Step in, Step out or to continue the script execution.
  • Click on a line number to set/remove a Breakpoint and use the console to get an variable for the current scope.
  • Use the arrow keys to browse through the history.

In this project used