You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a question about @babel/plugin-transform-react-inline-elements - how can I measure the performance boost that the plugin provides?
The plugin is used on the project I'm working on, but it causes a lot of errors in the browser console ("Warning: Each child in an array or iterator should have a unique "key" prop.").
I understand that the plugin should be used only in production mode and it is indeed only the production mode that has such errors. But still I'd like even production mode to not have the errors in the console. So I'm wondering if I can remove the usage of plugin, I'm wondering how the performance would change.
Thank you
The text was updated successfully, but these errors were encountered:
Hey @ilya-pyatin! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."
Hi, I have a question about @babel/plugin-transform-react-inline-elements - how can I measure the performance boost that the plugin provides?
The plugin is used on the project I'm working on, but it causes a lot of errors in the browser console ("Warning: Each child in an array or iterator should have a unique "key" prop.").
I understand that the plugin should be used only in production mode and it is indeed only the production mode that has such errors. But still I'd like even production mode to not have the errors in the console. So I'm wondering if I can remove the usage of plugin, I'm wondering how the performance would change.
Thank you
The text was updated successfully, but these errors were encountered: