11-Jul-2024
- β fix: fix missing whitespace when extracting plain text
- π docs: unify changelog entries
10-Jul-2024
- π» dev: conform with installed Astro's Node engine version
10-Jul-2024
- β breaking: property
headings
:PropHeadings
has been removed completely, headings are now automatically and ALWAYS removed - β breaking: property
renderer
:PropRenderer
has been removed completely, only text is rendered with HTML entities support ALWAYS enabled - πͺ feat: MDX support is added and enabled by default
- β fix: fix Markdown being rendered (#41)
- β fix: fix component import error
- π» dev: upgrade to
Astro
v4
- π» dev: set the Node requirement to
>=20
- π docs: change the description and documentation to match the new API (MDX support)
12-Sep-2023
- πͺ
feat: upgrade and test with
Astro
v3
- π» dev:
<PostExcerpt />
now comes with its own custom-built test suite and runner! (naive implementation π³)
13-Jul-2023
- π» dev: fix vulnerability, upgrade dependencies
30-Jun-2023
- β fix: upgrade dependencies, fixes multiple vulnerabilities
- β fix: better handle last character for smartEllipsis
- π» dev: add missing types
09-Apr-2023
- β fix: peer dependency install error (#32)
09-Apr-2023
- πͺ feat: add support for Astro v2 Collections
- πͺ feat: make the component backwards-compatible
- π» dev: migrate to Astro v2, check it out for breaking changes:
- migrate using Astro migration to v2
- π» dev: upgrade to Astro v2.2.0
Q: Can I NOT upgrade Astro?
A: Yes, but it's not recommended.
Q: Can I upgrade PostExcerpt
but not Astro?
A: Yes, all changes and new features are backwards-compatible.
Q: Can I upgrade Astro but not PostExcerpt
?
A: Look at the first answer.
Q: How do I upgrade Astro and migrate to v2?
A: Migrate your Astro project by going through the official migration guide.
Q: What do I need to do if I upgrade PostExcerpt
but not Astro too?
A: Nothing. Nada.
Q: Can I use Collections in Astro without upgrading PostExcerpt
?
A: No, Collections support is a new feature of PostExcerpt v>=2.x.x
.
Q: Okay, I want to upgrade both. Is there some reference code? π€
A: Sure, take a look at this component's testing environment, in particular the index page, which contains the post loops for Astro v<2 and Astro v>=2.
06-Apr-2023
- π» dev: improve IntelliSense
05-Apr-2023
- πͺ feat: add an HTML render (#18)
- πͺ
feat: add @igor.dvlpr/strip-html which brings:
- stripping of HTML code
- extracting of text content from HTML code
- πͺ
feat: add @igor.dvlpr/strip-html-headings which brings:
- stripping of HTML headings' code
- extracting of text content from HTML headings
- πͺ feat: detect ellipsis symbol in smartEllipsis
- β
fix: fix
trim()
sometimes not being applied - π» dev: move to TypeScript
- π» dev: fix missing typings
29-Mar-2023
- πͺ feat: preserve or strip post headings in the rendered excerpt (#12)
- β fix: broken integrations link (#16)
- π» dev: upgrade dependencies
- π» dev: make the test site public
- π» dev: update author link (#17)
16-Dec-2022
- π» dev: upgrade dependencies
- π docs: minor README fixes
02-Dec-2022
- πͺ feat: add smartEllipsis
- πͺ feat: add custom ellipsis support
- β
fix: fix
maxLength
issue (#10) - β
fix: use native <post>
.rawContent()
function - π» dev: refactor code
- π» dev: maintenance
- π docs: update JSDocs
13-Oct-2022
- π» dev: add testing environment
- π» dev: maintenance
12-Sep-2022
- π» dev: throw an error instead of logging it when required prop
post
is missing or not valid - π» dev: security fixes
12-Sep-2022
- π» dev: security fixes
- π docs: add an explanation how to fix a common Astro build error caused by Vite
11-Sep-2022
- π launch: initial release