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
When using rollup it has issues with RefForward and fills in the children and innerRef with undefined, undefined[(undefined, undefined)] respectively, which causes the exported bundle to not work. The only difference we could find when compared against Ref and RefFindNode was that RefForward imports PropTypes like import * as PropTypes from 'prop-types' whereas Ref and RefFindNode use import PropTypes from 'prop-types'.
Expected Result
To be able to export code that uses semantic using rollup with no issues
Actual Result
Exports RefForward with undefined props which brakes everything. It doesn't make sense that it has no issue with Ref and RefFindNode. So we think it has something to do with the way PropTypes is imported.
Version
0.86.0
The text was updated successfully, but these errors were encountered:
Bug Report
Steps
When using rollup it has issues with RefForward and fills in the children and innerRef with undefined, undefined[(undefined, undefined)] respectively, which causes the exported bundle to not work. The only difference we could find when compared against Ref and RefFindNode was that RefForward imports PropTypes like
import * as PropTypes from 'prop-types'
whereas Ref and RefFindNode useimport PropTypes from 'prop-types'
.Expected Result
To be able to export code that uses semantic using rollup with no issues
Actual Result
Exports RefForward with undefined props which brakes everything. It doesn't make sense that it has no issue with Ref and RefFindNode. So we think it has something to do with the way PropTypes is imported.
Version
0.86.0
The text was updated successfully, but these errors were encountered: