From 1d813c7c2a08e69db39b247719e7da736f1d8f42 Mon Sep 17 00:00:00 2001 From: philibeaux Date: Thu, 11 Jul 2024 14:26:13 +0200 Subject: [PATCH] docs(yalc): add documentation issue (#3989) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * docs(yalc): add issue related to yalc Signed-off-by: Alexandre Philibeaux * Update README.md Co-authored-by: Matthias Prost * Update README.md Co-authored-by: Clément Lafont --------- Signed-off-by: Alexandre Philibeaux Co-authored-by: Matthias Prost Co-authored-by: Clément Lafont --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2219d83afb..942bc79c4d 100644 --- a/README.md +++ b/README.md @@ -127,12 +127,15 @@ $ # If you do some changes into your package $ pnpm run build && yalc publish --push --sig # --push will automatically update the package on projects where it have been added, --sig updates the signature hash to trigger webpack update ``` -You can redo the same with `@ultraviolet/form` if you want to test it. +You can redo the same with `@ultraviolet/form` if you want to test it > :warning: since [1.0.0.pre.51 (2021-04-23)](https://github.com/wclr/yalc/blob/master/CHANGELOG.md#100pre51-2021-04-23), `yalc publish` needs the `--sig` option to trigger webpack module actual update. > :warning: `yalc` create a `yalc.lock` and updates the `package.json` in the target project. **Make sure to not commit these changes** +> :warning: if you are trying to yalc @ultraviolet/ui & @ultraviolet/form in your application and hope to see the change of @ultraviolet/ui into the component used by @ultraviolet/form you should be sure to not have any peerDeps of @ultraviolet/ui installed as it's will be resolve. If your are using pnpm and vite you can add `pnpm.override: { "@ultraviolet/ui": "$@ultraviolet/ui" }`. If this rfc is accepted this will solve our issue https://github.com/pnpm/rfcs/blob/main/text/0001-catalogs.md + + --- ## Versioning