chore: remove traces of @svelte-put/noti

vnphanquang · Jun 23, 2024 · ef0dbba · ef0dbba
1 parent 599e3aa
commit ef0dbba
Show file tree

Hide file tree

Showing 6 changed files with 5 additions and 15 deletions.
diff --git a/.changeset/config.json b/.changeset/config.json
@@ -12,3 +12,4 @@
   "updateInternalDependencies": "patch",
   "ignore": []
 }
+
diff --git a/.changeset/popular-emus-lay.md b/.changeset/popular-emus-lay.md
@@ -12,9 +12,9 @@
 '@svelte-put/avatar': patch
 '@svelte-put/resize': patch
 '@svelte-put/copy': patch
-'@svelte-put/noti': patch
 '@svelte-put/toc': patch
 '@svelte-put/qr': patch
 ---
 
 sync README.md and installation version in docs page
+
diff --git a/.changeset/pre.json b/.changeset/pre.json
@@ -12,7 +12,6 @@
     "@svelte-put/intersect": "3.0.0",
     "@svelte-put/lockscroll": "1.0.1",
     "@svelte-put/movable": "3.2.0",
-    "@svelte-put/noti": "1.1.0",
     "@svelte-put/preprocess-auto-slug": "1.0.1",
     "@svelte-put/qr": "1.2.0",
     "@svelte-put/resize": "3.0.0",
@@ -68,10 +67,9 @@
     "tiny-hounds-sing",
     "twelve-tools-type",
     "twenty-donkeys-serve",
-    "unlucky-beans-invent",
     "weak-peaches-smell",
-    "wet-meals-suffer",
     "wise-crews-destroy",
     "wise-points-own"
   ]
 }
+
diff --git a/.changeset/unlucky-beans-invent.md b/.changeset/unlucky-beans-invent.md
diff --git a/.changeset/wet-meals-suffer.md b/.changeset/wet-meals-suffer.md
diff --git a/sites/docs/src/routes/docs/architecture/+page.md.svelte b/sites/docs/src/routes/docs/architecture/+page.md.svelte
@@ -16,10 +16,11 @@ Packages within the `svelte-put` collection follow, as much as possible, the fol
 
 Because of the philosophies above, you will find that the majority of packages rely primarily on [svelte action](https://svelte.dev/docs/svelte-action) and [svelte store](https://svelte.dev/docs/svelte-store) to encapsulate only the necessary logics and leave the UI to be defined by users.
 
-The tradeoff, however, is that sometimes it takes verbose setup to achieve a desired system (in packages such as [@svelte-put/noti](/docs/noti) or [@svelte-put/tooltip](/docs/tooltip)). In my case, this forces me to "own" my code and get familiar with pieces of the package; if issues or customization demand arises, I will be more capable of providing solutions than say if I were to use a highly abstract prebuilt component.
+The tradeoff, however, is that sometimes it takes verbose setup to achieve a desired system (such as in [@svelte-put/async-stack](/docs/async-stack)). In my case, this forces me to "own" my code and get familiar with pieces of the package; if issues or customization demand arises, I will be more capable of providing solutions than say if I were to use a highly abstract prebuilt component.
 
 <p class="text-right text-sm">
   <a class="c-link" href="https://github.com/vnphanquang/svelte-put/edit/main/sites/docs/src/routes/docs/architecture/+page.md.svelte">
     Edit this page on Github
   </a>
 </p>
+
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,3 +12,4 @@
		"updateInternalDependencies": "patch",
		"ignore": []
		}