PatrickJS

thinking about it more. the Mitosis way is to support both since we support both ways with `` and `.map()` so I'll add support for both ``` function Layout(props) {...

I think we need optional linters to enforce the react-way vs html-way. For example one codebase may want to enforce every loop uses `` vs `.map`. We want the react-way...

This is with the CLI right?

yeah this is needed

I can work on a public webpack mitosis-loader/plugin and webpack playground to show raw, compiled components. We created a sample-page internally to check mitosis/core changes. We also used jsfiddle on...

yeah not documented because there were questions on what the angular/webcomponent version looks like

to create the context for angular. I still need to work on here. https://github.com/BuilderIO/mitosis/issues/330 but to consume context works correctly. For what you're doing there might be some questions on...

For webcomponent thats exactly how i wrote it and the context can be a Map instance

yeah this is needed. the workaround is not using function declareation. ```jsx export const usePrevious = () => {}; ```

@steve8708 what do you think?