Releases: ACP-CODE/astro-favicons
Releases · ACP-CODE/astro-favicons
v3.1.5
What's Changed
- Bump vite from 5.4.11 to 5.4.14 in the npm_and_yarn group across 1 directory by @dependabot in #52
Bug Fixes
- #53 Thanks @adleviton open the issue.
Full Changelog: v3.1.4...v3.1.5
Contributors
dependabot
Assets 2
v3.1.4
v3.1.3
What's Changed
- V3.1.2 by @JakiChen in #48
- Bump astro from 4.16.1 to 4.16.18 in the npm_and_yarn group across 1 directory by @dependabot in #49
Full Changelog: v3.1.2...v3.1.3
Contributors
JakiChen and dependabot
Assets 2
v3.1.2
Bug Fixes
- Fixed #46 currently,
<head>CAPO operations are only implemented for content between .- renderSync(ast) is no longer involved in rendering exceptions for some symbols between bodies.
- Revert back to the original state, manually or automatically insert localizedHTML between the head by manipulating the string.
Optimization and improvement
- Rethink the determination of the
isInjectedflag and optimize the execution logic of the middlewarewithCapo.
v3.1.1
What's Changed
- V3.1.1 by @JakiChen in #40
- Bump astro from 4.14.0 to 4.16.1 in the npm_and_yarn group across 1 directory by @dependabot in #44
New Contributors
- @dependabot made their first contribution in #44
Full Changelog: v3.1.0...v3.1.1
Contributors
JakiChen and dependabot
Assets 2
v3.1.0
Minor Updates
capotowithCapodefaulttrue(baseAstroConfig.compressHTML) & JSDoc Updated.- Manual Injected of HTML Tags Now Supported
e.g ~/components/Meta.astro
---
import { localizedHTML as favicons } from 'astro-favicons/middleware';
---
<meta charset="utf-8" />
<Fragment set:html={favicons(Astro.currentLocale)} />Manual or automatic depends on your convenience
v3.0.6
v3.0.2
Breaking changes
- New API interface, extensible Manifest supported by favilib
- Get the
<head>in order: Powered by and compatible withastro-capo(if infringement occurs, please inform us to remove it or seek improvements). inputAccepts multiple values, and specifies specific sources for different platformslocalizedSupported bymiddleware. (Please give us feedback if you have any questions. Thanks.) Currently, this is the most portable solution in my opinion. The alternative solution is to use component.- Live access, now you can access all assets generated by astro-favicons in development mode.
- Improved asset generation (provided by vite emitFile)
Minor Updates
- New default configuration
themesand defaultmaskableforandroid-chrome-512x512.png, please don't forget to change the value ofnameandshort_name