element-plus/packages/utils/package.json

{
  "name": "@element-plus/utils",
  "private": true,
  "license": "MIT",
  "peerDependencies": {
    "vue": "^3.2.0"
  }
}
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`{`
			`"name": "@element-plus/utils",`
refactor(utils): migrate utils (#5949) * refactor(utils-v2): migrate utils * refactor(utils-v2): migrate utils * refactor(utils-v2): migrate utils * refactor(utils): remove * refactor(utils): rename * refactor(utils): move EVENT_CODE to constants * refactor: remove generic 2022-02-11 11:03:15 +08:00			`"private": true,`
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`"license": "MIT",`
			`"peerDependencies": {`
fix: stop pinning vue peer dependency version (#3051) * fix: stop pinning vue peer dependency version It should be safe to trust `vue` to follow semver. Pinning a peer dependency version is a bad idea because any change in peer dependency requirement should be considered a breaking change in theory. On the other hand, `@vue/compiler-sfc` has a strict peer dependency version requirement. So pinning the `vue` version is likely to causing issues like https://github.com/vitejs/vite/issues/4573 in the future. * chore: update lockfile 2021-08-25 17:34:57 +08:00			`"vue": "^3.2.0"`
refactor(utils): migrate utils (#5949) * refactor(utils-v2): migrate utils * refactor(utils-v2): migrate utils * refactor(utils-v2): migrate utils * refactor(utils): remove * refactor(utils): rename * refactor(utils): move EVENT_CODE to constants * refactor: remove generic 2022-02-11 11:03:15 +08:00			`}`
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`}`