> This page is for Home.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.webflow.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.webflow.com/_mcp/server.

# Interactions support in DevLink export

> DevLink export now ships GSAP-powered Interactions (IX3) alongside Classic Interactions, with auto-generated per-export GSAP bundles and lazy-loaded runtime.

DevLink Component Export now ships interactions built with the new GSAP-powered Interactions engine.
Animations defined on a component, including triggers, timelines, and GSAP plugins, are exported and run in your React project with no extra setup.

## What's exported

For every component that has Interactions, DevLink now emits:

* **Interaction registration code**, wired through a new `useIX3Interactions` hook.
* **A per-export GSAP bundle** (`webflow_modules/devlink-gsap.js`) that contains only the GSAP plugins your site actually uses, such as `ScrollTrigger`, `SplitText`, and `CustomEase`.
  Plugin dependencies such as `CustomBounce` → `CustomEase` and `ScrollSmoother` → `ScrollTrigger` are resolved automatically.
* **The IX3 runtime bundle** (`webflow_modules/devlink-ix3.js`) that initializes GSAP and registers interaction data.

GSAP plugin selection is driven by the site itself.
No CLI flag or configuration is needed.

## One provider, both engines

The `<DevLinkProvider>` component now wraps both Classic Interactions (IX2) and the new GSAP-powered Interactions (IX3).
There is no separate `<IX3Provider>` component to compose:

```tsx
import { DevLinkProvider } from './devlink/DevLinkProvider';
import { AnimatedHero } from './devlink/AnimatedHero';

export default function App() {
  return (
    <DevLinkProvider>
      <AnimatedHero />
    </DevLinkProvider>
  );
}
```

Existing Classic Interactions setups keep working unchanged.

## Lazy by default

The IX3 runtime and GSAP bundle load on demand, only after a component that uses `useIX3Interactions` mounts.
Sites that don't use interactions, and pages that don't render an animated component, pay zero runtime cost: nothing is fetched and the bundles are never executed.

## Framework support

* **Next.js** (App Router and Pages Router, both Webpack and Turbopack): works in dev (StrictMode safe) and production builds.
* **Vite, Rollup, and esbuild**: dynamic import specifiers are statically analyzable, so chunks are emitted cleanly.
* **Astro**: works inside React islands.
  As with any React context provider, place a single `client:load` directive on the wrapping component.
  Two separate `client:load` islands won't share IX3 context.

## Requirements

* `@webflow/webflow-cli` v1.19.0 or later
* Node.js v22 or later

## To use

Update your Interactions so that they are scoped to the component that you'll export.
Then re-run the `webflow devlink export` command to pick up IX3 animations from your site.
No changes are needed in the `webflow.json` file.

For more information, see [What's exported](/devlink/docs/component-export/whats-exported).