Matthew Phillips

So what if we had a `steal-popular-packages` npm package that a dev just had to install that then autoconfigured? That would avoid the needing to include that stuff in steal...

# Proposal __tldr;__ Provide a new package that has preconfigurations for a variety of popular npm packages. > This was discussed on a [recent live stream](https://youtu.be/wUhv5zIUBv0?t=2432). ## Problem As stated...

We can do this, the question is, when to invalidate the cache?

I like that idea a lot, can you create a separate issue for that specifically?

Well, I think this issue is fine for that on second thought.

Thanks for filing the bug.

The file should be detected as es6 and run through a transpiler (either traceur or babel). In the old steal we had a js plugin that allowed things to be...

Will make a plugin for this in the new plugins API.

Couple of downsides: 1. Would make steal.js a big bigger (maybe even a lot bigger). Might be ok for dev, but not acceptable for production, so would need a way...

I also wonder how hard it would be to build something that's not a full-language parser but instead only looks for a couple of things: 1) some keywords (import/export) 2)...