framework

framework copied to clipboard

CHANGES IN THE NEXT RELEASE

• Lazy component loading with the nx.load(compName, loaderFn) function.
• Async component processing for heavy components with the heavy boolean component config property (It uses requestIdleCallback when it it supported with a setTimeout fallback).
• ES6 module syntax and tree shaking support.
• Total refactor of the core with support for custom components v1 (v0 and mutationobserver as fallbacks).
• Various performance improvements (especially on non chrome browsers).
• $process and $allow middleware metadata properties, that control which node types can be processed and which ones should throw an error when encountered.
• The same $process and $allow metadata properties for custom attributes.

FEATURES SCHEDULED FOR LATERS

• Cascading styles for quicker animations with less code (animate-middleware)
• Scroll middleware for scroll routing and scroll-into-view detection
• Limiters and filters for data-binding (bindable-middleware)
• Shadow DOM flavored slot styling for scoped styles (render-middleware)
• Dynamic and one time validation with a new validator util

The list is continuously edited. New ideas are added to it and when a feature makes it into a release it is deleted from here. Feel free to post feature suggestions in the comments! 🙂

@solkimicreb What are your thoughts on E2E testing with NX? Are you considering a particular framework like NighWatch or something else?

I don't know yet. Proper test coverage and testing guide lines are something that I will 100% surely add before the beta ends, but honestly I didn't start thinking about them yet. I don't think that I want to favor any E2E test libraries, probably I would provide multiple examples with the most popular frameworks and leave it to the users. What is your opinion?