@denkwerk/nuxt-favicon-generator weekly downloads statistics

@denkwerk/nuxt-favicon-generator

A complete favicon set for your Nuxt app, and a manifest or theme color with one option each, generated at build time from one SVG or a Figma component, served and linked for you.

Setup · Config file · Figma · Options · Overview

A Nuxt module that generates favicons and an Apple touch icon from one SVG, a raster image or a Figma component, serves the files, and adds the matching and tags to every page. Additionally, it can add a web app manifest, a theme color and Windows tiles. It is built on @denkwerk/favicon-generator.

• Nothing is written to public/: the files are generated into node_modules/.cache/favicon-generator at build time and served by Nitro. • Output is cached until the options or the source image change. A Figma export is reused while the Figma file is unchanged, which one small API request checks. • In nuxt dev, editing the source image restarts Nuxt with regenerated icons.

Setup

That generates and links favicon.ico, favicon.svg, favicon-96x96.png and apple-touch-icon.png. Additionally, you can add a theme color, a web app manifest and more:

Remove any favicon.ico or other icons from public/, because they would conflict with the generated ones. The module warns about this.

Config file

Instead of (or in addition to) the favicon options, the module reads a favicon.config.ts, the same file the CLI uses:

The lookup rules are the CLI's, starting in the Nuxt rootDir. The module uses the first of favicon.config.{js,ts,mjs,mts,cjs,cts,json} it finds, then checks parent directories up to the nearest one with a package.json or .git. Options in nuxt.config.ts take precedence over the file; groups are merged key by key, so the file can set manifest.name and nuxt.config.ts manifest.shortName. The file's output, overwrite and snippets are ignored because the module decides where files go, and its pathPrefix is relative to app.baseURL. favicon.config.ts is type-checked with nuxt.config.ts, and in nuxt dev editing it restarts Nuxt. Add @denkwerk/favicon-generator to your dependencies so the file can import defineConfig.

From Figma

The link must point at a node (node-id). The Figma REST API needs a personal access token with the file_content:read scope, which is read from the FIGMA_TOKEN env var or figmaTokenFile. Keep the token out of your config.

Options

Besides these module options, every @denkwerk/favicon-generator option except output, overwrite and snippets is supported: themeColor, appleTouchIcon, manifest, windows, legacy and the Figma token. Relative paths are resolved against the Nuxt rootDir.

| Option | Default | |

| input | none | Source image or Figma link. Nothing is generated without it. | | pathPrefix | / | Path under app.baseURL to serve the files from. / keeps /favicon.ico where browsers look for it. | | mirrorPrefixes | [] | More paths that serve the same files, e.g. ['/'] with pathPrefix: '/public/' to link them under /public/ and keep them at the site root. The tags use pathPrefix. | | head | true | Add the / tags to every page. | | cache | true | Reuse generated files while options and source are unchanged, and a Figma export while the Figma file is unchanged (one small API request per build checks it). false generates and exports on every build. | | cacheDir | node_modules/.cache/favicon-generator | Where the cache and the generated files are kept. | | configFile | looked up | Path to a specific config file, or false to ignore config files. | | enabled | true | Turn the module off, e.g. enabled: process.env.CI !== 'true'. |

app.baseURL is taken into account in all generated URLs and in manifest.json.

Examples

• examples/nuxt: options in nuxt.config.ts • examples/nuxt-config-file: options in favicon.config.ts

License

MIT

Description from the npm listing.