chore: update references after rename to angular-gsap/core

.github/workflows/release.yml

@@ -3,7 +3,7 @@ name: Release
 # Publishes @angular-gsap/core to npm via trusted publishing (OIDC):
 # no npm token is stored anywhere. npm verifies this workflow's identity
 # against the trusted publisher registered on the package's npm settings
-# (repo angular-gsap/angular-gsap, workflow release.yml).
+# (repo angular-gsap/core, workflow release.yml).
 #
 # Flow: run `pnpm nx release --skip-publish` locally (version, changelog,
 # tag, GitHub release); publishing the GitHub release triggers this.

README.md

@@ -40,7 +40,7 @@ GSAP itself is framework-agnostic and runs in any Angular app today, no wrapper
 
 GSAP's surface is enormous: tweens, timelines, position parameters, staggers, ScrollTrigger, SplitText, getters, utilities. Wrappers that re-expose it as directives or per-tween helpers cover a fraction of it awkwardly and go stale as GSAP evolves. What Angular actually makes hard is **lifecycle**: create animations after the DOM exists, scope selectors to your component, react to state, and clean everything up.
 
-That is the approach GSAP itself endorses with [`@gsap/react`'s `useGSAP()`](https://gsap.com/resources/React/). `injectGsap()` is its Angular equivalent, with signals replacing React's dependency arrays. It also adds something hard to hand-roll: signals read in the callback re-run it *after* the DOM has updated (`afterRenderEffect`), so animations always see fresh `@if`/`@for` output. The [Flip example](https://github.com/angular-gsap/angular-gsap/blob/main/apps/docs/src/app/pages/flip.page.ts) leans on this hard: capture layout before a signal changes the DOM, FLIP-animate after Angular renders.
+That is the approach GSAP itself endorses with [`@gsap/react`'s `useGSAP()`](https://gsap.com/resources/React/). `injectGsap()` is its Angular equivalent, with signals replacing React's dependency arrays. It also adds something hard to hand-roll: signals read in the callback re-run it *after* the DOM has updated (`afterRenderEffect`), so animations always see fresh `@if`/`@for` output. The [Flip example](https://github.com/angular-gsap/core/blob/main/apps/docs/src/app/pages/flip.page.ts) leans on this hard: capture layout before a signal changes the DOM, FLIP-animate after Angular renders.
 
 ## Install
 

apps/docs/src/app/app.component.ts

@@ -184,7 +184,7 @@ const DESKTOP = '(min-width: 64rem)';
         <a
           class="gh"
           hover="grow"
-          href="https://github.com/angular-gsap/angular-gsap"
+          href="https://github.com/angular-gsap/core"
           target="_blank"
           rel="noreferrer"
           ><svg

libs/core/README.md

@@ -33,6 +33,8 @@ export class Hero {
 
 ```sh
 pnpm add @angular-gsap/core gsap
+# npm install @angular-gsap/core gsap
+# yarn add @angular-gsap/core gsap
 ```
 
 ## Plugins and global defaults
@@ -50,6 +52,6 @@ Every GSAP plugin is free and ships in the `gsap` npm package: ScrollTrigger, Sp
 
 ## Documentation
 
-Full docs, patterns, and a live example app: [github.com/angular-gsap/angular-gsap](https://github.com/angular-gsap/angular-gsap)
+Full docs, patterns, and a live example app: [github.com/angular-gsap/core](https://github.com/angular-gsap/core)
 
 MIT licensed.

libs/core/package.json

@@ -14,7 +14,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/angular-gsap/angular-gsap.git",
+    "url": "https://github.com/angular-gsap/core.git",
     "directory": "libs/core"
   },
   "keywords": [

package.json

@@ -87,7 +87,7 @@
   "description": "GSAP integration for Angular — signal-reactive, SSR-safe animation contexts",
   "repository": {
     "type": "git",
-    "url": "https://github.com/angular-gsap/angular-gsap.git"
+    "url": "https://github.com/angular-gsap/core.git"
   },
   "author": "Luis Castro <luish.castroc@gmail.com>",
   "packageManager": "pnpm@11.21.0",