Closed HFmaS closed 1 year ago
@HFmaS can you reproduce the issue in a code sandbox (linked from the issue template)?
Interesting, the template didn't pop up for me when I created this issue initially, maybe because this was my first time opening an issue?
Unfortunately, I wasn't able to reproduce this behavior in the code sandbox, so I guess this behavior is due to an unexpected interaction with one of the other packages we're importing or an issue with how webpack is bundling our code.
@HFmaS one thing you try is making sure you're on the latest version of @blueprintjs/core and @blueprintjs/select
@HFmaS Any resolution for this? I am hitting this error as well.
@HFmaS Any resolution for this? I am hitting this error as well.
It was an issue with react-popper. The package-lock.json was pulling in the wrong version, presumably due to one of the other libraries we're using. Adding react-popper 2.2.4 to our package.json dependencies fixed it.
Environment
I'm making a new component and trying to use MultiSelect2. I've starting by providing only the required props (itemRenderer, items, onItemSelect, selectedItems, and tagRenderer), but I'm seeing an error inside MultiSelect2 which blows up the page: "Uncaught TypeError: placement is undefined". I tried passing explicit "placement" values through popoverProps and popoverContentProps, but neither seems to affect this issue. When I swap the original MultiSelect in for MultiSelect2, the error goes away, and the MultiSelect component renders as expected. What am I missing here?