Wrapping propTypes with an environment check instead of removing them

[insin]

Would it be feasible to wrap propType definitions in a if (process.env.NODE_ENV !== 'production') check (extracting them out first if they're part of a React.createClass()) instead of removing them completely?

This plugin is great and solves the problem of removing my own redundant propTypes for production, but it would be cool if it could also be adopted by authors transpiling reusable components to publish to npm, so your dependencies' propTypes could be available in development and test as normal, but automatically removed for production via the usual dead-code elimination process.

Could that be made an option into this plugin? Remove vs. move/wrap?

[oliviertassinari]

but it would be cool if its could also be adopted by authors transpiling reusable components to publish to npm

That sounds like a very good idea!
E.g. on one of my project, I'm letting Babel going through the source files of https://github.com/callemall/material-ui so I can remove the propTypes.

[oliviertassinari]

I'm working on it, it shouldn't be too hard, I'm already doing it here https://github.com/oliviertassinari/babel-plugin-transform-dev-warning/blob/master/src/index.js#L23.

[oliviertassinari]

@insin I have done a first iteration for this feature. I still miss the stage-1 class static syntax.

[insin]

Amazing, thanks!

Looking forward to integrating this into my React component build setup 👍

[oliviertassinari]

@insin I'm gonna add it to Material-UI too 🎉 .
However, I haven't tested it on a real project yet.
⚠️ It's still experimental.

I have two unsupported cases:

• The old React.createClass.
• The unnamed class.
  That should only be edges cases that we could support with more effort.