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

es-spawn

v1.0.9

Published

es-spawn =======

Downloads

2

Readme

es-spawn

Install

npm install --save es-spawn

Usage

script.js

import path from 'path';

function p(){
    return new Promise((resolve, reject)=>{
        setTimeout(()=>{
            resolve(path.join(__dirname, __filename))
        })
    });
}

async function myAsync(){

    let val = await p();
    console.log('The current path is ', val);
}

myAsync();

run.js

import spawn from 'es-spawn';
//const fork = require('es-spawn'); //Using commonjs

spawn('./script.js').then(child=>{
    //Nothing needs to be done here
    //unless you want you want to use ipc messaging.
}).catch(err=>{
    console.log('test ERROR ',err);
});

API

The interface for es-spawn is identical to node's child_process spawn. The only exception is that only javascript files can be used. In other words es-spawn works like a fork of a node process.

spawn(command, argv, options) -> child_process

You can run the fork as if you were using require('child_process').spawn.

About

es-spawn uses rollup, and babel.

rollup is used to compile es2015 modules in your script to commonjs require type modules.

babel is used to compile async functions down to generators.

These are the basic steps that es-spawn goes through when running a script.

  1. A temporary file is created, and the source script is read.
  2. The source script is compiled with rollup, and babel.
  3. Globals are altered to make the script string look like it's source.
  • __filename
  • __dirname
  • process.arg[1] = __filename
  1. The new script string is written to the temporary file.
  2. The path of the temporary file is passed to child_process.fork()

The most recent version of nodejs uses almost all of es2015. For this reason only es2015 modules, and stage-3 presets are compiled by es-spawn.

You can still use a .babelrc file to get more out of babel. Place a .babelrc file in the directory that contains the file you want to run with es-spawn.

If you want polyfills you should use ponyfills instead. Though most es2015 build-ins are supported by the latest node version. You can use the babel polyfills as well.

Happy coding!