Inferno: Roadmap 2016

[trueadm]

Upcoming roadmap for Q1-Q2 2016.

• [X] Break inferno into separate packages, such as: inferno-dom, inferno-server, inferno-component
• [X] DOM node/component hooks
• [ ] inferno-test-utilities
• [ ] DOM node transitions
• [x] Server side rendering
• [ ] Chrome dev tool extension
• [ ] propTypes
• [x] Performance optimisations
• [x] When refs are strings, imply the same logic as React and add them to their component like this.refs.node
• [ ] Documentation
• [x] External libraries that we deem essential: inferno-router and inferno-redux
• [x] Solve polyfill/legacy browser problems

[yak77]

Hi,

Just started looking at inferno, and the performance looks very impressive.

I was wondering if there are plans for TypeScript integration such as creatng a ".d.ts" definition file?

Also, does inferno support animations? If so, what is the recommended approach?

Thanks.

[ghost]

Hey, @yak77. Thanks for looking at Inferno.

Regarding TypeScript all I can say just now is that we will see what the future brings. Important for us now is to split Inferno in to three packages, and optimizations. Soon as that is done, we will see where the road will take us.

Animation is not directly supported. However Inferno supports all CSS properties that your browser supports. A difference from other frameworks. So transform works. You can find a transform example in the example folder. Transitions are not supported, but CSS animation property are.

There is no recommended approach for CSS / animation. Just use it the normal way :)

I hope my answers helped you :)

[kuraga]

@trueadm add "Solve pollyfills problem" and "Browser testing CI" :smile:

[terinjokes]

@trueadm did you have any immediate plans/ideas for what inferno-test-tools would look like? I'm currently really missing tooling to do Shallow Rendering (and simulating some browser events).

[stevenvachon]

Some ideas: http://blog.bitovi.com/change-propagation/

[trueadm]

@stevenvachon thanks for the link! I'll try and adopt that where possible :)

[Gouigouix]

What! "Inferno is supported by BrowserStack" and there are no browser test ;o)
TypeScript support :+1:

[iby]

TypeScript! TypeScript! TypeScript! :+1:

[buzinas]

:+1: TypeScript! :)

[buzinas]

Just saw that the new dev branch was migrated to TypeScript. That's awesome, congrats!

[trueadm]

@buzinas Thanks :) I'm enjoying TS too. It's massively improved since I tried it out a few years ago.

[buzinas]

Yeah, @trueadm, TypeScript today is all about Javascript Next with types. If you use VSCode is even better with its code intellisense, linting etc.

[trueadm]

@buzinas I am indeed using VSCode – really enjoying it too. Although, lack of global find and replace is a bit annoying!

[buzinas]

Any ETA for the DOM node transitions? By the way, is there a simple way to do that today?

[trueadm]

@buzinas Well, I've put a lot of thought into this. The way Snabbdom does transitions means integrating it into the core virtual-DOM layer, which isn't flexible. There are many ways of doing animation: JS, CSS3 and canvas. I thought it's best to be left to an exposable user-land library rather than being handled in core. Let me know if you think this a wrong decision.

[buzinas]

@trueadm While working on some big projects using React, I always played with other libraries to see how the community is evolving some good ideas from them.

A couple of weeks ago, I started developing some smaller apps, and I decided to give Inferno a try (have been flirting with it for the last months). I loved the way you made the logic for createBlueprint and the performance overall.

Also, it's great to have hooks for stateless components, and that you tried to keep the footprint as small as possible. I'm really enjoying to work with Inferno overall. Now I'm trying to give some boost for my application, performing some CSS transitions, and I saw that you were thinking about adding to the core that transition attribute, I loved it.

I know it's less flexible, but it doesn't mean you must always use that, right? If you need something more complex, you can do Javascript animations etc. I'd love to have some simple CSS3 animations with one single attribute, as you suggested in the other post.

I can't say it was a "wrong decision", because it's something too particular, but what I can say is that I think some CSS3 transitions into the core is something that increases development productivity and pleasure. It's something we use nowadays in any application - specially mobile focused ones.

[stevenvachon]

I plan to write a vanilla version of jquery.transitionsend with web animations support in the future. It could be used to handle the completion of transitions.

[buzinas]

Any thoughts, @trueadm?

By the way, is there any example of CSS transitions in Inferno?

[trueadm]

@buzinas that's some valid uses of it. I'll look into this for Inferno 1.0. I haven't made any CSS transition examples with Inferno – but I do know some people that have (by using inline style).

[Centaur]

Since version 1.0 has been released now, I think a project template/generator like angular-cli/create-react-app/ember cli ... will be very useful for newcomers like me to try inferno out.

[trueadm]

@Centaur hasn't been released yet as stable. It's still in alpha. I hope it will be stable within the next week. Once it is, looking at something like you mentioned is definitely on the cards!

[Centaur]

@trueadm Looking forward to that. Thank you.

[lucsky]

An external library that I would deem essential as of today would be inferno-mobx.

[trueadm]

@lucsky There is a mobx-inferno package already out there, although third-party, rather than in the core repo. I plan on moving as many essential packages into the core Inferno monorepo.

[trueadm]

Closing this in favour of the 1.0 roadmap https://github.com/trueadm/inferno/issues/375