bigpipe / react-jsx Goto Github PK

Version 15.5.0 of react-dom just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As react-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.5.2 of assume just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As assume is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 6.21.0 of babel-standalone just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As babel-standalone is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

react-tools is being deprecated. Can we upgrade this to use babel-standalone?

Strict mode code may not include a with statement in index.js 29:10.

im want do example in clinet-side

but, this example only server-side.

so i want import this 'react-jsx' like in client-side

<script src="../somepath/react-jsx.js></script>

is this possible??

(originally posted at apollographql/apollo-client#4312)

Intended outcome:

On a Mutation component, it seems that the block must begin on a new line after the start tag:

const Submit = props => <Mutation mutation={DELETE}>
  {mDelete => (
    <Mutation mutation={UPSERT}>
      {mUpsert => (
        <input type="submit" value="Submit Changes" style={{ float: 'right' }}
          onClick={evt => submitAction({
            evt, returnTo: props.setPage, mDelete, mUpsert, refetch: props.refetch,
          })} />
      )}
    </Mutation>
  )}
</Mutation>;

Actual outcome:

if the curly brace is placed immediately after the start tag, then a runtime error occurs:
<Mutation mutation={UPSERT}> {mUpsert => (...

Error:

index.js:1446 Warning: Failed prop type: Invalid prop children of type array supplied to Mutation, expected function.
in Mutation (at SubmitCancel.js:82)

Versions

System:
OS: macOS High Sierra 10.13.6
Binaries:
Node: 10.12.0 - /usr/local/bin/node
npm: 6.5.0 - /usr/local/bin/npm
Browsers:
Chrome: 71.0.3578.98
Safari: 12.0.2
npmPackages:
apollo-boost: ^0.1.22 => 0.1.22
react-apollo: ^2.3.2 => 2.3.2

Currently data provided by mixins has to be passed explicitly, it would be nice if this would inherit automatically to childs. E.g.

var React = require('react')
  , ReactIntl = require('react-intl')
  , Pagelet = require('pagelet')

Pagelet.extend({
  view: 'view.jsx',
  get: function get(render) {
    var pagelet = this;

    var Component = React.createClass({
      mixins: [ReactIntl.IntlMixin],
      render: function () {
        // The offending (lack of) scope, passing this is 
        // required to get methods and data from the mixin.
        return pagelet.template('./my-component.jsx', this);
      }
    });

    return render(void 0, {
      Component: Component,
      intlData: { locale: 'us', messages: [{}] }
    });
  }
}).on(module);

Version 15.5.1 of react-dom just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As react-dom is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴