Skip to content

Migration & deprecations for Vue

Markdown
Loading…

Deprecated option names that still work, the current name for each, and the console warning that points you here.

A few option names are deprecated. They still work, but log a [cookieyes] warning, and they will be removed in a later release. If you see one of these warnings, or copied an older snippet, use the current name:

WhereDeprecatedUse insteadNotes
app.use(CookieYes, config) option mode"offline""cookie-only"Same behaviour, clearer name
app.use(CookieYes, config) optionbackendURLapiUrlUnder mode: "self-hosted"
app.use(CookieYes, config) optionoverrides: { regulation }regulation at the top level
app.use(CookieYes, config) optionbuiltInIntegrations: [{ vendor: "meta" }]integrations: [metaPixel({ ... })], with presets from @cookieyes/scriptsThe presets also load the tool after consent. See Integrations
TypeScript type exported by the packageConsentRuntimeOptionsCookieYesConfig

If both an old and a current name are set, the current one wins. The one exception is integrations and builtInIntegrations: both run, so remove the old entry once you add the preset, or the vendor's events are counted twice.

Everything else is unchanged: components, composables, styling, translations and categories keep the same names, and the same configuration object works in every CookieYes package.

Next steps

On this page