Element ref was specified as a string (trigger) but no owner was set. about react-dropdown-tree-select HOT 3 CLOSED

This issue arises when you have multiple copies of react being loaded on the page. Its hard to pinpoint what is causing this without having more details but few common pitfalls are misconfigured webpack/npm dependencies.

E.g., misconfigured externals in webpack:

// bad:  
externals: {
  'react': 'react',
  'react-dom': 'ReactDOM'
}

// good 
externals: {
  'react': 'React',  // main entry point of React starts with capital R
  'react-dom': 'ReactDOM'
}

Another solution would be to delete mode_modules (destroy it completely, including any symlinks) and doing npm install again.

Make sure only one version of React is specified in your dependencies (including dev and peer dependencies).

from react-dropdown-tree-select.

@mrchief Thank you for your response - you helped fix the problem

Yes it was dependancy issue – I realise I am using React@16 but have a number dependancies that list React@15 in their dependancies. I managed to add a fixed alias to my Webpack configs.

config.resolve.alias.react = path.resolve(__dirname, 'node_modules', 'react')

Through my Googling I come across the recommendation that libraries should not list React in their dependancies but instead should use peerDependancies (devDependancies is fine). Should I create a pull request to do that?

from react-dropdown-tree-select.

Should I create a pull request to do that?

Sure would love to have a PR on that!

from react-dropdown-tree-select.