According to the react-select documentation, noOptionsMessage and loadingMessage must be passed strings. Utils.js calls these functions without the required arguments, which will break if the messages use the strings they expect to be passed.
A workaround is to simply return an empty string if these functions are called with no arguments. This does not seem to affect the displayed message.
According to the react-select documentation, noOptionsMessage and loadingMessage must be passed strings. Utils.js calls these functions without the required arguments, which will break if the messages use the strings they expect to be passed.
A workaround is to simply return an empty string if these functions are called with no arguments. This does not seem to affect the displayed message.