-
-
Notifications
You must be signed in to change notification settings - Fork 182
Closed as not planned
Labels
Description
Describe the bug
Steps to reproduce
- Setup a vite with ssr project by 'vite-ssr'.
- Add ant-design-vue@^3.2.7
- Add
<a-select mode="multiple">into component, select multiple options. It renders close icon for selected options in input and checked icon in popover, but each icon just render once. - Only one selected options in
<a-select>has remove icon.
What is expected?
All selected options should have remove icon after its label whether ssr or not.(Works fine in normally command vite)
What is actually happening?
Only one selected options in <a-select> has remove icon.
I thought this may be a bug of vite-ssr, so I have also tested in vite-plugin-ssr(reproduction link), problems still exist, so I think this may be a vite's bug.
Reproduction
https://stackblitz.com/edit/vitejs-vite-evglmf?file=src%2FApp.vue
System Info
System:
OS: macOS 12.4
CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
Memory: 2.23 GB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 10.23.2 - ~/n/bin/node
Yarn: 1.22.17 - ~/n/bin/yarn
npm: 6.14.10 - ~/n/bin/npm
Browsers:
Chrome: 103.0.5060.53
Firefox: 100.0.2
Safari: 15.5
npmPackages:
@vitejs/plugin-vue: ^2.3.3 => 2.3.3
vite: ^2.9.12 => 2.9.12Used Package Manager
npm
Logs
Click to expand!
vite v2.9.12 dev server running at:
> Local: http://localhost:3000/
> Network: use `--host` to expose
-- SSR mode ready in 3313ms.
vite-ssr doesn't appear to be written in CJS, but also doesn't appear to be a valid ES module (i.e. it doesn't have "type": "module" or an .mjs extension for the entry point). Please contact the package author to fix.Sorry for my English.
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
vcasy and omerbugraoz