@purple/phoenix-components 5.8.0 → 5.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +0 -0
- package/README.md +4 -0
- package/dist/bundle.cjs.js +1 -1
- package/dist/bundle.cjs.js.map +1 -1
- package/dist/bundle.esm.js +2 -2
- package/dist/bundle.esm.js.map +1 -1
- package/dist/bundle.umd.js +1 -1
- package/dist/bundle.umd.js.map +1 -1
- package/dist/index.d.ts +10 -11
- package/package.json +151 -141
- package/CHANGELOG.md +0 -853
package/LICENSE
CHANGED
|
File without changes
|
package/README.md
CHANGED
|
@@ -24,6 +24,10 @@ Phoenix Components takes advantage of some 3rd party libraries to create consist
|
|
|
24
24
|
|
|
25
25
|
[Phoenix Components Storybook](https://purple-technology.github.io/phoenix-components)
|
|
26
26
|
|
|
27
|
+
## Deployment process
|
|
28
|
+
|
|
29
|
+
Before merging to master run `npm run release:feature`, this will create a new version tag. After that you can merge your branch to master and from there you can run `npm run release:publish`.
|
|
30
|
+
|
|
27
31
|
## Install
|
|
28
32
|
|
|
29
33
|
`npm i @purple/phoenix-components`
|