Because rollem.config.js is loaded using Node require we can use JavaScript there.
Make an example

Hi!

Please take a look at the following files:

package.json

{
  "name": "issue",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "rollem": "rollem -c rollem.config.js",
    "rollemWatch": "npm run rollem -- --watch",
    "rollup": "rollup -c rollup.config.js",
    "rollupWatch": "npm run rollup -- -w"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "rollem": "^1.10.0",
    "rollup": "^0.41.4",
    "rollup-watch": "^3.2.2"
  }
}

rollup.config.js

export default {
  entry: 'src/index.js',
  dest: 'dist/script.js'
};

rollem.config.js

export default [{
  entry: 'src/index.js',
  dest: 'dist/script.js'
}];

Finally create an src folder with an index.js in it with any content.

If you run npm run rollupWatch, then the bundle gets built first and gets rebuilt after every change.
Opposed to this when you run npm run rollemWatch, there is no building of the bundle, it only gets built once you do any changes in the source file.

When I am trying to import relative module, like it doesn't work. For example, the following rollem.config.js fails

import helper from './my-helper';

export default [/* ...entries... */]

Gives me an error Error: Cannot find module './my-helper.js'

It happens because you are using eval that uses require from the current module context, but not the original rollem.config.js location.

See how that was worked around in Rollup. I think that this trick with temporary replaced require hook should be ported there as well.

The watch-glob module uses a very outdated version of gaze and it seems to be an unnecessary wrapper around it. The watch script should use gaze directly, instead of watch-glob.

Merge source folders to watch only the top level one

['src/foo', 'src', 'src/foo/bar'] 
// should watch just ['src']

Rollup 0.42+ as per rollup/rollup#1389

Instead of all of them, for rollup/rollup#863

I made rollem.config.js:

import typescript from 'rollup-plugin-typescript';
import multiEntry from 'rollup-plugin-multi-entry';

export default [{
  entry: './src/scripts/Main.ts',
  dest: './dist/index.js',
  format: 'iife',
  plugins: [typescript()]
}, {
  entry: 'test/**/*.ts',
  dest: './dist/test.js',
  format: 'es',
  plugins: [
    multiEntry(),
    typescript()
  ]
}];

and executed this command:
rollem -c rollem.config.js --watch

then I received:

Treating 'rollup-plugin-typescript' as external dependency
Treating 'rollup-plugin-node-resolve' as external dependency
Treating 'rollup-plugin-commonjs' as external dependency
Treating 'rollup-plugin-json' as external dependency
Treating 'rollup-plugin-multi-entry' as external dependency
[06:30:31 GMT+0000 (UTC)] watching source folders for changes [ 'src/scripts', 'test/**' ]
/home/ubuntu/workspace/node_modules/watch/main.js:73
    if (err) throw err;
             ^

Error: ENOENT: no such file or directory, stat 'test/**'

Please check this issue.
Thanks.

See comments in rollup/rollup#863

I've made some experiments with rollup-stream and rollem to try to glue them together and it seems it would be much easier if we simply added an option like options.stream. Instead of simply returning a list of destination, it could be a stream. This would allow us to use other Gulp modules more easily.

I created a simple example, where I'm trying to give multiple entries to rollem with the multi-entry rollup plugin. See the attached rollemtest.zip for the source.

If I execute rollem -c rollup.config.js, then it works fine. If on the other hand I try executing rollem -cw rollup.config.js, it throws the following error (assuming, that I'm standing in the C:\wamp\www\rolluptest\ folder):

path.js:7
    throw new TypeError('Path must be a string. Received ' + inspect(path));
    ^

TypeError: Path must be a string. Received true
    at assertPath (path.js:7:11)
    at join (path.js:466:7)
    at Object.<anonymous> (C:\wamp\www\rolluptest\node_modules\rollem\bin\rollem.js:11:20)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.runMain (module.js:575:10)
    at run (bootstrap_node.js:352:7)

If I replace rollem with rollup (version 0.41.4), then both codes work without a problem.
See rolluptest.zip for this other case.

crashes

Allow passing list of plugins

import nodeResolve from 'rollup-plugin-node-resolve'
export default {
  entry: 'src/out-spec.js',
  plugins: [ nodeResolve() ],
  targets: [
    { dest: 'cypress/integration/out-spec.js', format: 'umd' }
  ]
}

In fact the problem is in this line. Existing code must be replaced with this one:

const configFilename = (argv.c === true) ? 'rollem.config.js' : argv.c;

it would be cool if there where file globs for entry dist setups so you can have

a.js -> a.bundle.js
b.js -> b.bundle.js
c.js -> c.bundle.js

if you want to bundle each file in a folder individually.

When the cli is running for a long time, and the output of single build x bundles rows are higher the the max visible row count in the window, there is no visual feedback if the package have been built or still compiling because the console window content will be the "same" visually.

A build (date)time should be added to the message. Eg:

let timeString = new Date().toLocaleString('en-US', { hour: '2-digit', minute: '2-digit', second: '2-digit', hour12: false });
console.log('[%s] built %d bundles', timeString, configs.length)

Thoughts?

At the beginning of the test, it first tries executing the following command:

cd test/es5-config; npm test

Windows says, that it fails to load this directory. Tested it in MINGW32 (Git Bash) and Windows 7 CMD.

I'm using rollup with rollem. In my rollem.config.js, when running rollem --watch as an npm script, if I import modules like this:

const nodeResolve = require('rollup-plugin-node-resolve');
const babel = require('rollup-plugin-babel');
const uglify = require('rollup-plugin-uglify');

everything works fine. If I do this instead however:

import babel from 'rollup-plugin-babel';
import nodeResolve from 'rollup-plugin-node-resolve';
import uglify from 'rollup-plugin-uglify';

everything still works, but now I get the following warnings:

'rollup-plugin-babel' is imported by rollem.config.js, but could not be resolved – treating it as an external dependency
'rollup-plugin-node-resolve' is imported by rollem.config.js, but could not be resolved – treating it as an external dependency
'rollup-plugin-uglify' is imported by rollem.config.js, but could not be resolved – treating it as an external dependency

As stated, everything works just fine (things get built), but it's still an annoying (and seemingly unecessary) warning.

I could be missing something and Rollem already does what I'm looking for, but wildcards would be ideal in the context of building a module for unit testing where each export in a file within a directory is added to a CJS module...

gulp.task "build:module", ->
    rollEm [
       
        entry: "./src/main/js/example/app/**/*/.js"

        format: "cjs"
        dest: "./dist/app.js"
    ]

The wildcard entry ./src/main/js/example/app/**/*/.js would prompt rollem to iterate the directory...

What do you think?

https://github.com/bahmutov/rollem/blob/master/package.json#L57

Based on the standard js' codebase, there is no -w flag and adding so will make standard ignore paths specified after it and instead run the formatter for the whole codebase.

I suggest removing -w from the script.