Matteo Figus

@jackbush-rl this is for now the source of truth for any updates and we have no target date yet

I can tell you that in our case, often, we handle this scenario by having some kind of "skeleton" page that already includes the component by making a request to...

I like that. Perhaps if component's package.json would have a `oc.files.test = [{ 'testname': 'test.html'}]` with test.html being something like ```html ... {{renderedComponent}} ...and/or ... ``` Then we could use...

As promised, this is my proposal (simplified): 1) No limits on making people webpack their own deps into the server.js (but we may want to expose the possibility to hook...

@navamgupta I don't think this will be a problem if declared as `devDependencies`. This should affect only `dependencies` and only if really "required/imported" inside the server.js (as webpack bundling includes...

I think we should be able to using https://github.com/debopamsengupta/requirey for that. The API I suggest is: 1) Configuration from array of dependencies goes to array of dependencies including (optionally) the...

@mattiaerre I think the easiest use case I can think about is the registry using [email protected] which has a security issue and want to upgrade to [email protected] which fixes but...

This is interesting. Just to understand a bit more, can you give me an example of your scenario when you need properties to dynamically change and then re-rendering of nested...

Sure!

Hi @NimaSoroush - as far as I remember, the domain library has been pending deprecation since node 6, but still on the pending state, while they finalize a replacement API:...