element-plus/packages/utils/package.json

{
  "name": "@element-plus/utils",
  "version": "0.0.5",
  "license": "MIT",
  "peerDependencies": {
    "vue": "^3.2.0"
  },
  "scripts": {
    "clean": "rimraf dist",
    "build": "gulp"
  },
  "gitHead": "c69724230befa8fede0e6b9c37fb0b7e39fd7cdd"
}
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`{`
			`"name": "@element-plus/utils",`
refactor: update package path and bundle folder (#3016) 2021-08-24 13:36:48 +08:00			`"version": "0.0.5",`
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"`
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`},`
Revert "build!: simplify build & support native esm import (#3900)" (#3945) * Revert "build!: simplify build & support native esm import (#3900)" This reverts commit fb94222bb443b8267616b96f0afd27756293aa5d. * remove module * Fix linter * Add @element-plus/icons as dependency * update pnpm lock file * temporary lock element-plus at 1.1.0-beta.20 2021-10-20 09:42:32 +08:00			`"scripts": {`
			`"clean": "rimraf dist",`
			`"build": "gulp"`
			`},`
refactor: update package path and bundle folder (#3016) 2021-08-24 13:36:48 +08:00			`"gitHead": "c69724230befa8fede0e6b9c37fb0b7e39fd7cdd"`
feat(core): add avatar components 2020-08-02 18:27:46 +08:00			`}`