Matthew Phillips

I'm cool with this as long as these "middle level" mixins are created. I believe an end user shouldn't have to choose between high-level things like superMap and super low-level...

Is there a can-reflect way to do this yet @phillipskevin @justinbmeyer ?

I kind of agree, but also am not sure if this is metadata that anything other than can-define would have. It's certainly not generic in the way that get/set on/off...

Going to do this first: https://github.com/canjs/can-event/issues/30 And then update this PR to use that.

Not quite ready to merge, there's still an issue here.

cc @justinbmeyer

Could the packagemap script have a property on it, `packageMap` or something so you could use: `document.querySelector('#mymap').packageMap` to get it? Not sure if there is precedent for properties on elements...

I think this is a good idea. I've already seen people be confused by this.

This looks ready to go, anything that's being waited on?

I like the idea of migrating to snapshots here. However it looks like from the code that you still need to add the manual `want{}`, so I think we should...