TypeScript support?

[idchlife]

I'm trying to use it with typescript but I'm kinda new to it. What exactly does default export of gibbon looks like? Is it function?

Not clear what to do with such included module in bundle:

As I can tell, it's just declaring var gibon inside module and not exporting it anywhere, so module just returns empty Object.

[tunnckoCore]

@idchlife 👍 need to update the build flow, cuz currently its main export is IIFE (as seen in the sourcemap url)

I'll provide UMD, CJS and ES builds, so users can use what they want.

As about TS, don't know, i'm no using it and don't understand such things. But kinda support and like @sindresorhus's position sindresorhus/ama#439. So it is more likely i don't add TS file here. But PRs for such is welcome too, but someone should maintain it.

[tunnckoCore]

Btw UMD bundle is currently available, but for browsers.

What you use? Kinda feel Browserify? That's a bug currently for Browserify users, because they resolves the IIFE, not the UMD/ES.

[idchlife]

webpack with ts-loader. I'll think about adding definition to Definetely Typed in spare time

[tunnckoCore]

webpack with ts-loader.

hm.. that's strange than why it resolves the IIFE build, maybe webpack does not understand pkg.module field? huh

I'll think about adding definition to Definetely Typed in spare time

Great to hear and thanks! Ping me when you done the PR there, so i can learn something, haha :)

[idchlife]

@tunnckoCore I'm trying to configure webpack so it would use "main" from package.json and not "browser". Somehow it ends up using "browser" script.

What else uses "browser" field in package.json? Browserify? Trying to understand what's going on wrong with my config here...

update:
Some digging and questioning and I discovered that when webpack sees "browser" field it uses exactly it without chance to config it to use another field. Wow. Unexpected.

[tunnckoCore]

Damn. That's sad, but yea one more reason why unpkg/unpkg#25 is a problem and why I won't use/set browser field any more. I was thinking that Webpack understands module and jsnext:main, because I heard that somewhere.

Thanks in any way, I'll update the things this night or tomorrow at least.

edit: can we verify that Webpack not repsects these fields when not see browser field? If that's true, is totally sad, otherwise the problem will be fixed with just removing the browser field.

[idchlife]

@tunnckoCore if talking only about webpack - version 2 was recently released. And it has richer resolving functionality than in version 1. So now problem is solved, thank you for thinking about this with me!

[tunnckoCore]

that is what i was talking about, yea. i was sure it can be fixed outside of gibon