Conan Albrecht
Conan Albrecht
+1 Just another vote for this. Overall, I really like your implementation, but the constructor and `update` having different behavior was a gotcha for me. It seems like they should...
Awesome! I am encouraged by your response and questions. I also can appreciate the need for backwards compatibility. There are straightforward answers to your questions, but I can't write the...
FYI, here's the current npm stats on the bundlers. `webpack` is still the goliath and is going strong. Their last release supposedly did a lot to alleviate the "config hell"...
> How to proceed with sourcemaps and the location to store them? Let me try to summarize how the TypeScript parcel plugin works. It's a good example of how all...
> I get your point about modules having to reside in the npm repository, but what exactly does that mean for e.g. the re module? It won't be named `__init__.py`...
> Having modules like re, math and iterator on npm is bound to lead to name conflicts. But I'd like to keep the original Python module names and import syntax....
Feel free to PM me if you want to set up a F2F call to discuss any of this. Also be sure to check the diff on the actual transcrypt...
A thought on the backwards compatability... I agree you can't leave people hanging in the dust. Especially after the change to ES6 that just happened. I'm not sure what the...
FYI I'm implementing some of these things today (`parcel-bundler` branch, not in `master`).
Status report: The changes to transcrypt to allow direct plugin use are almost done. I'll probably finish it tomorrow.