Peter Burns

Hm, I've just tried this scenario out and I was able to jump to the definition of an element defined in a JS file that was imported using ``. Is...

Ah, tricky tricky. I see three options in the short term (long term we would like to add first class typescript support): 1. teach the analyzer to recognize that style...

As a first step, a more structured representation of the cleanup passes, and the ability to control them a la #1. If we get enough cleanup passes a plugin model...

Currently it's hardcoded to the PolymerElements org unless you specify the repos using the `--repo` CLI arg. With configurable passes & repos then it's much more likely to be useful...

We've made some progress on this, but currently all passes need to be checked into tedium itself. How should tedium discover other passes that you'd like to run?

Ah, yeah, the latest stable version of typescript has a bug with inferring generic types :( Fortunately the beta channel is very stable. Try this: `npm install typescript@beta` and try...

I think I can bang out something to solve the dependencies and devdependencies capitalization issue very safely. I don't have time to test the bigger change of enforcing more standard...

Given the goal to allow a specifier to resolve to a built-in module, it would be better to require `./`. Taking the example from the readme: ```json { "imports": {...

This builds on top of https://github.com/caridy/redefine-custom-elements/pull/3 to make it easier to merge them both, if you look at just the second commit the change is clearer

This builds on top of https://github.com/caridy/redefine-custom-elements/pull/3 to make it easier to merge them both, if you look at just the second and third commits the change is clearer