Another one that would be helpful is the remaining lifecycle hooks, in particular the willDestroy hook.
-
-
-
Hm is willDestroy not implemented yet?
-
Unless i screwed something up. :) There is a open issue to implement these:https://github.com/glimmerjs/glimmer-component/issues/16 …
-
Ah good call. Shouldn't be too hard. Last week was a bit of decompression due to EmberConf being over but we're back to business.
-
there's a PR for wilDestroy too https://github.com/glimmerjs/glimmer-component/pull/42 …
End of conversation
New conversation -
-
-
unify ember-cli pipeline + fastboot :)
-
Yes yes yes. The temporary pipeline divergence should be over soon.
End of conversation
New conversation -
-
-
Test blueprints.
-
Gooood call.
End of conversation
New conversation -
-
-
nested tracked properies.
-
You can nest tracked properties by putting an instance of a class inside of an instance of a class.pic.twitter.com/hFFVEjK6C9
End of conversation
New conversation -
-
-
I found the distinction between internal properties and external arguments to be confusing. How do I use an @ arg in the component.ts code?
-
`this.args` -- if that's not documented, it should be!
End of conversation
New conversation -
-
-
Transparent integration with npm modules or a way to import them into the build (à lá ember-cli).
-
Yeah this is a huge priority and honestly something that is very close but didn't make it for initial release. On its way!
-
I think this actually more or less works, although you will get a warning from the TS compiler. Packages do need to be Rollup-compatible.
-
What npm package did you have in mind? Something with a `module` field in its package.json or no?
-
Yes that is correct TDizzle
-
we're having pretty good results with a webpack/rollup friendly ESM (ES5 + ES Modules) and a UMD for other cases
End of conversation
New conversation -
-
-
I wrote a blog post about it: https://www.ludovf.net/blog/taking-glimmerjs-for-ride/ …

-
This is great feedback, thanks!
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.