These are chat archives for pixijs/pixi.js

16th
Nov 2016
Chad Engler
@englercj
Nov 16 2016 02:39
cannot find module error from gulp usually doesn't have anything to do with TS
likely just that it can't resolve that module
anyway we can see your project layout? and what version of pixi you are using?
cellopoly
@cellopoly
Nov 16 2016 03:07
Hello I have a quick question about 4.1.1
I can get my app to compile using webpack and version 4.0.3
but when I upgrade to 4.1.1 I get an error in devtools trying to access _pixi2.default
just wondering if anyone could help me or provide some guidance
cellopoly
@cellopoly
Nov 16 2016 03:26
oh nevermind figured it out
I was using import PIXI from 'pixi.js'
after looking at the exports in pixi now i need import {Container} from 'pixi.js'
or this which is pretty cool import * as PIXI from 'pixi.js';
Chad Engler
@englercj
Nov 16 2016 04:02
correct
you had to do that before too
but babel hide that from you
Andrew
@Andrew50851467_twitter
Nov 16 2016 05:09

Yeah sorry I don't have it up anywhere but it is laid out simply as:

dist/
src/
.. main.ts (imports pixi)
vendor/
.. pixi.js, pixi.js.d.ts

my gulpfile has just one task

gulp.task("default", function () {
return browserify({
basedir: '.',
debug: true,
entries: ['src/main.ts'],
cache: {},
packageCache: {}
})
.plugin(tsify)
.bundle()
.pipe(source('bundle.js'))
.pipe(gulp.dest("dist"));
});

cellopoly
@cellopoly
Nov 16 2016 09:32
@englercj Totally missed that post. Thanks for the clarification
Andrew
@Andrew50851467_twitter
Nov 16 2016 21:03
Further I am using atom and atom-typescript... when my import is "import * as PIXI from 'pixi.js'" atom has no problems picking up the definitions etc.