Matthew Conlen

It sounds like what you have is in the right direction. What are the specific issues that you are running into? The setup that I was imagining is: 1) there...

Ah yeah, so as it stands, if a component is created/serialized during the compile process it won't be available until the next time idyll runs because of the way that...

@rollaball - is it possible to wrap this logic for users? E.g. - they write something like -- ``` function setup() { ... } function draw() { }; ``` and...

I think there may be a way to use the approach that is used [in the runtime to solve this issue](https://github.com/idyll-lang/idyll/blob/master/packages/idyll-document/src/utils/index.js#L138-L148), namely using `eval()` to force a particular context. Then...

More info on this technique to inject a context here: https://stackoverflow.com/questions/8403108/calling-eval-in-particular-context

But its possible that this is just over complicating the issue. In that case I think ```` ```exec:p5 p.setup = function() { }; p.draw = function() { }; ``` ````...

This seems reasonable to me @c4ffein. If this solution is fairly ergonomic (which it seems like it is, except for the peer-deps/ssr issues) then it is probably more sustainable to...

FWIW this already exists as a language feature (you can `npm install some-great-component`) and use it in idyll like `[SomeGreatComponent /]`. The change would just be to the syntax. We...

I'd be open to having a conversation about including a plot.ly component. Honestly I don't know enough about the plotly API to comment on how much that makes sense. IMO...

I'd love to see this implemented as a new npm module