question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Warning in production caused by babel react optimisation

See original GitHub issue

I’m running an erb app packaged in an appImage and it seems that react is not running in production mode because it showing warning about unique key prop. 46846520_316213875459604_8759571953217437696_n Normally this type of message don’t show up in production mode.

I’m not able to reproduce the same behavior with the command DEBUG_PROD=true yarn build && yarn start. I have several pages my app and some of it shout this type of message.

After investigating a little it seems this “issue” with babel transforms is related

Prerequisites

  • [ x] Using yarn
  • [ x] Using an up-to-date master branch
  • [x ] Using latest version of devtools. See wiki for howto update
  • [ x] Link to stacktrace in a Gist (for bugs)
  • [ x] For issue in production release, devtools output of DEBUG_PROD=true yarn build && yarn start
  • [x ] Tried solutions mentioned in #400

Expected Behavior

Don’t show react warning in packaged app

Current Behavior

react warnings are showns in react packaged app

Your Environment

  • Node version :
  • Version or Branch used : master
  • Operating System and version : ubuntu 18.04

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
amilajackcommented, Dec 19, 2019

It was fixed

1reaction
amilajackcommented, Nov 28, 2018

Please file a bug for that repo

Read more comments on GitHub >

github_iconTop Results From Across the Web

Optimizing Performance - React
By default, React includes many helpful warnings. These warnings are very useful in development. However, they make React larger and slower so you...
Read more >
How do you configure Webpack to clear the React Warning for ...
When deploying React apps to production, make sure to use the production build which skips development warnings and is faster.
Read more >
How to fix build failures with `create-react-app` in production
Look into your build logs, and find any warnings printed by your build command. Fixing those warnings will make your build succeed again...
Read more >
An in-depth guide to performance optimization with webpack
A good understanding of webpack's underlying principles can vastly improve your bundle size, application performance, and user experience.
Read more >
How We Reduced Our React App's Load Time by 60% - InfoQ
Using React by itself will not result in a highly performant application. If you're not careful, the application can pick up bloat easily....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found