To be backwards compatible the TKO library needs to be polyfilled. Examples of ES6 features that need polyfill:

• Generators
• Object.entries/Object.assign
• Backticks
• => functions
• Spreads

Here are some things needed to polyfill:

• WeakMap (?)
• Object.assign / entries
• Promise
• Generators
• Map + Set
• Node.remove
• Symbol, Symbol.interator / observable
• String::star

Comments

• Regarding accessibility, what about ARIA attributes?
• About search engines in SEO, what about DuckDuckGo and Yahoo?
• Nothing about DevTools or debugging ?
• Technically PostCSS is not really a preprocessor but a postprocessor (like for example Autoprefixer, that seems to be missing by the way).
• Technically R

目前已有的模式

逻辑复用在 React 中是经历了很长的一段发展历程的， mixin -> HOC & render-props -> Hook

逻辑重用

相信很多接触过 React Hook 的小伙伴已经对这种模式下组件间逻辑复用的简单性有了一定的认知，自从 React 16.7 发布以来，社区涌现出了海量的 Hook 轮子，以及主流的生态库 react-router，react-redux 等等全部拥抱 Hook，都可以看出社区的同好们对于 Hook 开发机制的赞同。

其实组件逻辑复用在 React 中是经历了很长的一段发展历程的，mixin -> HOC & render-props -> Hook，mixin 是 React 中最早启用的一种逻辑复用方式，因为它的缺点实在是多到数不清(REACT是学院派前端库, mixin多了容易导致

Certified users are users found on 'https://ulogs.org/discover' or 'https://steemit.com/@uloggers/followed'. Steemgigs has an algorithm currently that pulls users on this list and provides them extra ui-perks e.g a 'delegate button' or a 'certified badge'. See image:

We

See: palantir/tslint#4534
TSLint will be deprecated, ESLint will succeed TSLint for TS linting.

Equivalent ESLint configs should be created to enable a smooth transition.