All Projects → alexisvincent → Systemjs Config Builder

alexisvincent / Systemjs Config Builder

Generate SystemJS config files from node_modules

Programming Languages

javascript
184084 projects - #8 most used programming language

SystemJS Config Builder

Generate SystemJS config files from node_modules

Overview

The easiest way to include modules in SystemJS is currently through JSPM. This project aims to provide an alternative, by leveraging the deterministic installs of Yarn (also works with npm) and generating config files to explain to SystemJS how to resolve modules from node_modules.

Roadmap

  • [x] Trace node_modules and build registry
  • [x] Generage compatability configs for packages
  • [x] Generate valid SystemJS config file
  • [x] Make sure loading React.JS works
  • [x] Cache registry (to speed up subsequent generations)
  • [x] Use own @node polyfills. See #1 for progress
  • [x] Respect jspmPackage: true
  • [x] Perform path optimisations (nm: -> node_modules), for smaller configs
  • [ ] Fully support npm resolve algorithym (upper node_module and single dep node_modules)
  • [ ] Allow simple local overrides
  • [ ] Use JSPM overrides
  • [ ] Allow dependency filtering (so we don't include deps meant for just the server)
  • [ ] Provide CLI flag to optimize generated.config.js
  • [ ] Allow configurability
  • [ ] Make more robust

Currently, given this package.json, SystemJS Config Builder generates this config.

Usage

Example Project (with usage instructions)

You can test the generation via the cli in systemjs-tools.

yarn global add systemjs-tools

add SystemJS @node browser polyfills

yarn add systemjs-nodelibs

and generate the config

systemjs config

optionally you can also add a postinstall hook to do this automatically

package.json

{
  "scripts": {
    "postinstall": "systemjs config"
  }
}

Thanks

Thanks to Juha Järvi for helping me flesh out this idea and for the discussions regarding his awesome cbuild project.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].