nodemon like option

I love estrella, hope you will continue to work on it.

Some users probably have a scenario where they would like to start a the resulting code using node any time the source changes. Usually this is done using nodemon. I wrote a little workaround, not being sure if this is a smart way to do it:

#!/usr/bin/env node

const pkg = require('./package.json')
const common = require('./build.config.js')
const { spawn } = require('child_process')
const { build } = require('estrella')

let node

build({
  ...common,
  entry: 'src/index.js',
  outfile: pkg.main,
  onEnd(config, result) {
    if (config.watch) {
      if (node) {
        node.kill('SIGHUP')
        node = null
      }
      if (result.errors.length > 0) {
        console.error(`Build failed with ${result.errors.length} errors`)
      } else {
        console.info(`Build succeeded. Launching 'node ${pkg.main}'`)
        node = spawn('node', [pkg.main], {
          shell: true,
          stdio: 'inherit',
        })
      }
    }
  },
})

In case it is, it would be great to get an estrella option to say, start the outFile with node, like:

#!/usr/bin/env node

const pkg = require('./package.json')
const common = require('./build.config.js')
const { buildAndRun } = require('estrella')

buildAndRun({
  ...common,
  entry: 'src/index.js',
  outfile: pkg.main
})

Thanks!

[rsms]

Landed in v1.2.0 which was just released.

API: https://github.com/rsms/estrella/blob/v1.2.0/estrella.d.ts#L93-L130

Example: https://github.com/rsms/estrella/tree/v1.2.0/examples/run

@holtwick let me know what you think and how it’s working for you. Thanks for the collaboration!

[holtwick]

Thanks @rsms for adding the feature. In general, it works great.

Some little things might be nice: to have as well:

• Add the run option’s documentation to the README.md file
• In my PR I added a -r or -run option. It seems to be missing here. It is important, because if somebody wants to build for production, the code is still run. Alternatively the code should only be executed if -w is active. A workaround would be to handle this in the build.js script itself, but that’s not very attractive IMO.