Provide NPM package

[legomind]

It would make it very convenient for those of us using webpack or browserify

[vieron]

+1

[novwhisky]

+1

[Diligentia-Uitgeverij]

This issue can be easily be avoided using browserify-shim.

[novwhisky]

Not as easy as npm install easeljs would be. Package management and build systems are related but distinct problems.

[legomind]

browserify-shim wont help webpack users.

[Diligentia-Uitgeverij]

I know it's not as easy, and that browserify-shim won't help webpack users. But it is a valid point for browserify users that are looking for a way to install, as long as there is no NPM-package.
My comment was not made to talk down at anyone, just to help people find a way to pass the issue without having to wait on the team to add a package.

As for webpack users, webpack seems to have options to import bower modules, or to shim packages that are not correctly formatted.

I haven't used webpack myself, so I can't really help there, but seeing as there are options, I would imagine that this isn't the highest priority on the teams mind.

[jamesplease]

Are the maintainers interested in providing an npm package? If so, I'm willing to help get things set up for publishing this on npm; I can make a PR for the package.json and/or provide guidance on npm best practices. Lmk if any of this could help get this issue closed out!

[K3TH3R]

This doesn't solve the fundamental problem of module importing in Webpack. However, I figured out a nice way to bypass this until a solution is presented by just "importing" the classes from the window global object. I put up a Gist which demonstrates this and also shows how to use it with ES6 syntax/ classes: https://gist.github.com/iamkether/752e381e03ddcb78f637

[gskinner]

Hi All - just wanted to pop in to let you know that this is one of our priority items for the next release. We have a plan in mind that we will run past you here in a bit, but we are very open to thoughts on specific implementation details.

[Robinfr]

Any update on this?

[fatlinesofcode]

unofficial package here, https://github.com/mattbalmer/createjs-collection

[Robinfr]

We have our own in-house package for createjs that's not the point. I would like to have an official one.

[toverux]

For Webpack users, here is a "verbose", but fully-functional configuration:

Install EaselJS via Bower: bower install --save EaselJS

Install these Webpack loaders: npm install --save-dev imports-loader exports-loader (these are very useful to use libraries that export their symbols with legacy ways, like attaching them to window)

In your webpack.config.js, merge your config with:

module.exports = {
    module: {
        loaders: [
            // That will tell Webpack that EaselJS refers to `window` with `this` and exports `window.createjs`.
            { test: /bower_components\/EaselJS\/.*\.js$/, loader: 'imports?this=>window!exports?window.createjs' }
        ]
    },

    plugins: [
        // This will tell Webpack how to find the main file of bower modules
        new webpack.ResolverPlugin(
            new webpack.ResolverPlugin.DirectoryDescriptionFilePlugin('.bower.json', ['main'])
        )
    ],

    resolve: {
        // Add bower_components as a modules root
        modulesDirectories: ['node_modules', 'bower_components']
    }
}

Now, if you use ES2015, you could do in your app:

import { Stage } from 'EaselJS';

const stage = new Stage(canvas);
// enjoy!

[Entaro]

Hi,
toverux solution works fine.