yosuke-furukawa / react-nl2br Goto Github PK

View Code? Open in Web Editor NEW

78.0 4.0 17.0 160 KB

Newlines to <br /> for React

License: MIT License

JavaScript 100.00%

react nl2br

react-nl2br's Introduction

react-nl2br

USAGE

const nl2br = require('react-nl2br');
const result = nl2br('aaa\nbbb\nccc\nddd');
console.log(result); // aaa, ReactElement('br'), bbb, ReactElement('br'), ccc, ReactElement('br'), ddd

in jsx

const React = require('react');
const nl2br = require('react-nl2br');
var Hello = React.createClass({
  render: function() {
    return (
      <div>Hello {nl2br(this.props.name)}</div>
    );
  }
});

INSTALL

$ npm install react-nl2br -S

react-nl2br's People

Contributors

Stargazers

Watchers

Forkers

hoto17296 sutiwo flepretre chocoby federicobond spahi4 ivandovgal williamboman shuheiktgw sidferreira haydnhkim stefen lorenzos thomasglachant tetsugi joshuabaker

react-nl2br's Issues

Produces a warning if you use multiple nl2br's on one page

Warning: Each child in an array or iterator should have a unique "key" prop.

React should be a peerDependency, not a dependency of react-nl2br

We noticed that we were getting a second copy of React included in our application bundle, and this was due to react-nl2br declaring React as a dependency.

Since the expectation would be that the host project would be using React, and you want react-nl2br to use the host project's copy of React, react-nl2br should list React as a peerDependency in package.json, not as a dependency.

Correct versioning

Hey,

The last version release is 0.0.3, but the previous one was 0.1.0.
In order to work correctly with semver, we need to release a new version that should be 0.2.0, then replublish on npm.

iterator should use key

When I use your nl2br I get:
Warning: Each child in an array or iterator should have a unique "key" prop.

Cannot install v1.0.0 because of wrong dependency version constraint

The package.json requires @types/react@^16.14.0. However, the latest version of @types/react is 16.9.56.

The numbering of @types/react does not run parallel to react.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

npm

package.json

@types/react 18.2.18

mocha 10.0.0

react ^15.7.0 || ^16.14.0 || ^17.0.0 || ^18.0.0

Check this box to trigger a request for Renovate to run again on this repository

Can you please add an open source license, MIT maybe?

In order to use this, we need there to be an open source license. I'm happy to submit a PR adding it for you if you are OK with MIT.

Warning in Next.js 13 (and maybe React 18?)

When I use this in my Next.js 13 project, I get the following warning in the console:

Warning: A props object containing a "key" prop is being spread into JSX:
  let props = {key: someKey};
  <br {...props} />
React keys must be passed directly to JSX without using spread:
  let props = {};
  <br key={someKey} {...props} />