Bundle command

[matthewp]

Use case

Often times you might want to create a bundle that is not associated with a production build. This is just a bundle of modules that can be used by steal.

A common use-case would be bundling dependencies that do not change often (such as dependencies that are npm installed).

API

Two forms:

cli

steal-tools bundle some/filter/**/*

Node

stealTools.bundle({}, {
  filter: "some/filter/**/*"
});

[matthewp]

Vague implementation steps

1. - Create a standalone stealTools.bundle that creates a single bundle from a given filter.
2. - Make it so that the configuration for those packages are included in the bundle.
3. - Try to get it to load by mapping the @dev module: { map: { '@dev': 'my-bundle' } }`

[matthewp]

Note that this will be a minor release. I'd rather do a prerelease and let this bake for a little while to get an idea of the API is right or not.

[matthewp]

Will probably add a convenience shorthand for the use case of bundling node_modules:

steal-tools bundle --dev

Which should expand to:

stealTools.bundle({}, {
  filter: "node_modules/**/*",
  dest: "dev-bundle.js"
});

[matthewp]

"steal": {
  "map": {
    "@dev": "dev-bundle"
  }
}

[matthewp]

@m-mujica I would like to extend this out so that we can avoid having to load the package.json!npm at all in development.

The difference between this and what you've done so far is that in this "mode" it would not add the npmPackages, but instead it would leave in the config (and its deps) in the bundle.

I think this should be under some different flag. I'm not sure what those flags should be off the top of my head. Maybe something like:

Bundles only node_modules:

steal-tools bundle --deps

Bundles node_modules + package.json!npm (and its deps):

steal-tools bundle --dev

🤷‍♂️ Feel free to explore better names.

[matthewp]

Fixed by #612