Webpack + RequireJS interoperable shared libraries
JavaScript HTML
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
docs
lib
test
.eslintrc-client
.eslintrc-server
.eslintrc-server-test
.gitignore
.istanbul.func.yml
.istanbul.server.yml
.npmignore
.travis.yml
CONTRIBUTING.md
HISTORY.md
LICENSE.txt
README.md
index.js
package.json

README.md

RequirePack

Webpack + RequireJS shared library interoperability!

Travis Status Coverage Status

Sauce Test Status

Webpack and RequireJS both can consume AMD code straight up. Which means if you are in a transitional / complex scenario where you want some code to load with Webpack and other code to load with RequireJS from the same code base you can!

And, Webpack and RequireJS both have facilities for sharing libraries across entry points. Unfortunately, if loading both RequireJS and Webpack entry points on the same page, the applications cannot natively use the same shared library.

RequirePack bridges this gap by providing an interopability layer to allow a Webpack-generated shared library to be consumaed by RequireJS entry points.

Getting Started

Install:

$ npm install --save requirepack

Configure:

TODO(8): Document Configuration

Development

Ports various servers run on:

  • 3001: Static / demo server.
  • 3030: Ephemeral server for functional tests. Override via TEST_FUNC_PORT environment variable.

Topics

  • Shared Libraries: A deep dive into how shared libraries work in RequireJS, Webpack and are bridged with RequirePack.
  • Tests: Our test suite encompasses a lot of different types of builds that are likely to be encountered, running demos, and