breaking-change: add nuxt-3 support

[ivodolenc]

Type of Change

• Breaking change

Request Description

• Adds support for Nuxt 3
• Adds TypeScript support
• Separates all premium plugins from the default ones (supports both with types)
• Transfers the repo to the new Hypernym Studio organization

Since Vite/Rollup doesn't fully support dynamic import of node modules, I split the premium ones from defaults and add each plugin (only club plugins) to own file.

I chose that way because premium plugins are not available in the node_modules directory unless the user installs them manually (default ones are automatically installed when user installs gsap pkg), so importing them into the plugin (client/browser side) without dynamic imports or some kind of magic won't work.

It should also be noted that GSAP offers 3 types of paid packages, including bonuses, and each package offers different plugins, so it can easily become a code mess (not all club plugins are installed with the same license).

This separation method of premium plugins seems to me to be the best option at the moment, because the user chooses which plugins want to activate. Also, all plugins, default and premium, are automatically registered and fully typed so the dev experience are great.

Additional Details

I also want to mention that I will be transferring the repository to my new Hypernym Studio organization and renaming the package to @hypernym/nuxt-gsap.

So when the changes are merged into the main branch, the module will be installed and used with the new name, everything else remains the same:

Example

npm i -D @hypernym/nuxt-gsap

// nuxt.config.ts

{
  modules: ['@hypernym/nuxt-gsap'],
}

TODO

• Add documentation
• Add simple usage examples

Resolves #24