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

nodesfc

v0.9.0

Published

Single File Code - package.json-free node scripts

Downloads

8

Readme

Single File Code

Single File Code, or sfc, allows to execute NodeJS scripts and methods with its dependencies. defined in the script itself. Either via cli or via module

Instead of having a package.json file and installing the dependencies via npm commands, you can specify the dependencies in your script comments.

SFC will take care of installing the dependencies.

example

/**
 * @dependency lodash latest
 */
require('lodash').map([1,2,3,4], n => console.log(n))

/**
 * @dependency faker latest
 */
let fake = require('faker').fake('{{name.lastName}}, {{name.firstName}}')
console.log(fake)

It supports --watch for your development-phase things.

Installation

Use your terminal to install sfc as a globally availabe package.

npm i nodesfc -g

Cli usage

Usage: nodesfc [options] <file>

Options:
  -V, --version  output the version number
  -d, --dryrun   Removes node_modules and package-lock.json before installing dependencies.
  --debug        Enables debug messages.
  -w, --watch    Watch for changes in the file
  --noupdate     Opt-out of update version check
  -h, --help     display help for command

Example:
  $ nodesfc --watch example/file.js

Specifying dependencies:
  /**
   * @dependency lodash latest
   */

To get help, execute:

nodesfc -h

Library usage

You can invoke a JS file in two different ways.

Invoking an specific method (like in AWS Lambda)

This will return the method's result - as it is.

let lib = require('nodesfc')

let r = await lib.init({
  method: 'handler', // Name of the method to be executed
  methodArgs: ["hello", "world"], // List of parameters to apply
  file: './export-handler.js'
})

console.log(r)

// { firstParameter: 'hello', secondParameter: 'world' }

The init method returns a Promise with the method's result.

Executing an entine NodeJS script

This will return the full std output as an array.

require('nodesfc')
  .init({
    file: 'my_javascript_file.js', // File to execute
    env: { // Optional k->v pairs of custom environment variables
      CHARACTER: 'Jon Snow'
    }
  })
  .then(result => console.log({result}))

/*
  {
    "stdLines": [
      {
        "output": "1",
        "err": false,
        "date": "2019-08-14T11:47:21.821Z"
      },
      {
        "output": "2",
        "err": false,
        "date": "2019-08-14T11:47:21.821Z"
      },
      {
        "output": "3",
        "err": false,
        "date": "2019-08-14T11:47:21.821Z"
      },
      {
        "output": "4",
        "err": false,
        "date": "2019-08-14T11:47:21.821Z"
      },
      {
        "output": "Boyle, Alek",
        "err": false,
        "date": "2019-08-14T11:47:23.063Z"
      }
    ],
    "code": 0
  }
*/

The init method returns a Promise with an object with the properties:

  • stdLines being an array of objects containing the STD outputs for both errors and logs. In the same order as they were triggered.
    • output string - the actual text logged
    • err boolean - determines if the log was sent to std-err or not
  • code number - the execution exit code.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

License

MIT