Kyle Robinson Young

Did more digging, I think the issue is because the type from the `external` isn't the Kotlin type but actually the generated `.js` type: ```kt package thing @KustomExport class Item(...

Correct. The wrapper `thing.js.Item` has an instance of `thing.Item`. But I think because the `internal` class it's wrapping is not exposed, the names are mangled: The `CommonItem.exportItem(): Item = Item(this)`...

That is a good idea. I tried with converting the `external`s to be `interface`s and that fixes some instances where it knows to unwrap such as this: ```kt fun getItemAt(at:...

Got a chance to try that. Passing the proxy via a setter/fun didn't work but if pass the list from the proxy via a setter, it works with interfaces. This...

@glureau Oh by chance, would you be able to do a release of https://github.com/deezer/KustomExport/commit/adc689cc192aaa58c106d0d3c06467d6a7c9fba3?

Fantastic, thank you! It's working well for me.

I think it might be impossible for webpack to have a generic node stream interface like browserify and closure. Since webpack can output multiple files and needs to know a...

I see two options: 1. A PR to webpack that implements a stream interface where one could pipe in a single or multiple entry points. Then stream out virtual files...

Wow thanks @sokra! I didn't know `compiler.outputFileSystem` was a thing. @sindresorhus Would you mind if I gave you a PR for this implementation on gulp-webpack?

Thanks @sindresorhus! Using https://github.com/shama/gulp-webpack you can now do: ``` js var gulp = require('gulp'); var webpack = require('gulp-webpack'); gulp.task('default', function() { return gulp.src('src/entry.js') .pipe(webpack()) .pipe(gulp.dest('dist/')); }); ``` Let me know...