Kevin Newman

I have been trying to get this to work in a NativeScript app (through Svelte Native). I keep hitting various parsing or config errors. I wish I could point to...

I also have questions - why does it pull in a solid bundle, instead of individual packages? Is it because of a lack of a dependency graph? I wonder if...

I wonder if an alternative way to get the dep graph for an individual meteor package would be to set up a Package Proxy shim, and then load the individual...

It looks like meteor makes a separate file for each package now:  I'm inferring quite a bit here though. I'll look into that loader issue - this webpack config...

Well, it's a bit more complicated with `dynamic-imports` (I think since Meteor 1.5), though for webpack that's probably not relevant. I think the piece I'm missing is why it's necessary...

I tried it both ways - importing the js with ts-laoder using "allowJs", and with a "babel-loader" config I quickly ported from another project. Either way I get this error:...

I assumed the output got mangled - it's Windows after all..

This was straight forward. The path was getting output to a javascript string. On Windows, that means the backslashes need to be escaped. I simply replaced that one concatenation line...

I put it in a PR https://github.com/staeke/meteor-imports-webpack-plugin/pull/1

I ran in to the same problem. I'm pretty sure it had worked, but then it stopped. The difference seems to be in the what *context* is sent to the...