ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Node​Eval

by mediaupstream ST2

A Sublime Text Plugin that "evals" a selection/document with NodeJS

Details

  • 2014.01.02.23.47.49
  • github.​com
  • github.​com
  • 10 years ago
  • 2 hours ago
  • 11 years ago

Installs

  • Total 3K
  • Win 1K
  • Mac 984
  • Linux 491
Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 29 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

NodeEval Sublime Text 2 & 3 Package

Use the NodeJS binary to evaluate a document or selection(s) and print the results

Screenshots

Install

Installation via the Package Control (Search for NodeEval)

To install manually clone this project into your Sublime Text 2\Packages folder:

OSX

git clone git://github.com/mediaupstream/SublimeText-NodeEval.git ~/Library/Application\ Support/Sublime\ Text\ 2/Packages/NodeEval

Windows

git clone git://github.com/mediaupstream/SublimeText-NodeEval.git "%APPDATA%\Sublime Text 2\Packages\NodeEval"

Usage

After installation you will have:

  • Context Menu and Tools Menu items:
    • NodeEval - evaluate the current selection(s) / document with node
    • NodeEval - Continuous (Toggle) - Continually evaluate the current selection(s) / document with node. This command is a toggle for the current document / selection(s) only. You can set the refresh rate in the Sublime settings (see below)
  • Default keyboard shortcuts:
    • ctrl+n,e
  • Package Settings: Preferences > Package Settings > NodeEval
{
      // The absolute path to your nodejs executable
      // e.g. "/usr/local/bin/node" or "C:\\bin\\node.exe"
      "node_command": "/usr/local/bin/node",

      // How to output the results, options include:
      // - new [default] "send output to a new file"
      // - console       "send output to a new Panel (Console) view"
      // - replace       "overwrite the current file/selection with the output"
      // - clipboard     "there is no output, output copied to clipboard"
      "output": "new",

      // if output type is "new" the output is overwritten, set to false to append the output
      "overwrite_output": true,

      // if set to true the output is copied to the clipboard
      // if `output` is set to "clipboard" this value is ignored
      "copy_to_clipboard": false,

      // refresh rate threshold for "continuous" mode (in milliseconds)
      "threshold": 200,

      // Set any extra ENVIRONMENT Variables as an object
      // @example
      //    "env": {
      //      "NODE_PATH":"/path/to/node",
      //      "NODE_MODULES":"/path/to/node_modules"
      //    }
      // @note: if you start sublime from a terminal using `subl` your normal environment
      // variables should be available to you 
      "env": {}

    }

The commands work on a selection, multiple selections or if nothing is selected the whole document. Your script will be eval'd through nodejs in it's own thread.


Why not just use the NodeJS plugin, or the nodejsLauncher plugin ?
the NodeJS plugin is awesome, but it's also really bloated. also the nodejsLauncher only works on Windows.

Contributors

Derek Anderson
Shane Walker
Shesh
akira-cn
Jakub Gutkowski

License

MIT License