wildhoney / keo Goto Github PK

In React 16.0 createClass will no longer be a part of the react library but will still be available through the create-react-class library. I might be able to make PRs for these changes in a few days when I'm less busy.

Take a look at supporting Observables.

If I use the webpack raw-loader to load my CSS (see https://gist.github.com/alexlafroscia/f0b2493c1abebd28a22d7164832ddaa7), does the shadow function support loading the CSS that way?

Since this library is compiled using webpack is it possible to use it in react-native?

Say for example I have a need for refs when building a chat app and expecting the chat box to scroll down when new messages arrive.

Allows Promise.all/resolved individually for promise arrays.

Preact aims to deliver on a few key goals:

• Performance: Render quickly & efficiently
• Size: Small size, lightweight (approximately 3.5kb)
• Efficiency: Effective memory usage (recycling, avoiding GC thrash)
• Understandability: Understanding the codebase should take no more than a few hours
• Compatibility: Preact aims to be largely compatible with the React API. preact-compat attempts to achieve as much compatibility with React as possible.

http://jslog.com/2014/10/02/react-with-webpack-part-1/

Namely mapDispatchToProps and mergeProps

You mention it in the readme. Probably a typo

keo.js:151 Uncaught TypeError: Cannot read property 'subscribe' of null

Are there any suggestions or solutions to using Keo with Typescript? Thank you.

Is it possible to use the shadow function with ShadyCSS? Our project has to support older browsers (IE11).

Does this approach support the use of PropTypes?

I would like to use Keo to make React libraries, but it seems that it bundles all of React, ReactDOM, Redux etc. into the library. Is it possible to make them peerDependencies (as well as devDependencies for working on Keo itself) and list them as externals in the build?

Changing the typical behavior of a function called compose (R-to-L composition) could be confusing when it's used in a codebase that includes other, more standard implementations of compose. Consider following Ramda's lead and call the function pipe (and make compose R-to-L, just for good measure).

Seems that the new strict.js file is missing from the publish script. Am I missing something :)

Easier to debug than dealing with instances which look the same.

When installing Keo with Yarn I get the following error:

[email protected]: The engine "node" is incompatible with this module. Expected version "5.10.1".

This is because Keo has the following in the package.json:

"engines": {
    "node": "5.10.1"
  },

If Keo is truly dependent on this node version then this isn't an issue. Otherwise this is preventing those who are using Yarn from being able to install the package.

Is it possible to get this released to npm for React 0.15.x compatibility?

Hi,

I have just tried to update the react dependency of React to version 16.
This version of React separates DOM Factories from the react library (react-dom-factories). Also, I have updated react-router to a version which supports React 16.

Unfortunately, the example is not working anymore. There are multiple identical errors indicating a TypeError - Cannot read property 'toLowerCase' of undefined.

The source of the problem is the Function getRootHostContext(rootContainerInstance) in the ReactFiberReconciler.

This function gets called multiple times with different node Types.

The internal of the function creates a valid object (toLowerCase function is working) if the rootContainerInstance is of section type - section-todo-app (2x from the start in the example). The object is invalid if the rootContainerInstance is a document-fragment.

Any suggestions ...

Thanks!

I'm currently using react-redux 5.0.3 and redux 3.6.0. This will be really helpful if they are updated.