Version Packages

[frontibotito]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@frontity/components@1.8.0

Minor Changes

• 2f988427 #826 Thanks @michalczaplinski! - Make the Image component from @frontity/components AMP-aware and remove the Intersection Observer fallback which used to lazily load images in the absence of native lazy loading.

@frontity/core@1.14.2

Patch Changes

• a154a9cb #840 Thanks @luisherranz! - Fix Webpack/TS-Node excludes not working on Windows.
• 63154b4f #837 Thanks @luisherranz! - Fix transpilation of frontity.config.js files in external packages.

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[luisherranz]

#837 is the fix that makes #834 not needed anymore 😆

I'm going to push a revert of that PR.

[luisherranz]

I think that fixes it.

[SantosGuillamot]

Okay, great. Thanks @luisherranz 🙂

[DAreRodz]

The create-symlinks tests in @frontity/core were failing (see this). They were failing in my local environment as well, and I've made them pass just updating the package-lock file.

Let's see if that fixes the error.

[DAreRodz]

Uhm, weird, I didn't fix anything... 🤔

[SantosGuillamot]

Mmm, if they are passing locally, could be something related to npm? I remember we have had issues in the past because we use npm 7 and GitHub actions use npm 6.

[DAreRodz]

Mmm, if they are passing locally, could be something related to npm? I remember we have had issues in the past because we use npm 7 and GitHub actions use npm 6.

Actually it's failing with node 16 and npm 7.

[DAreRodz]

OK, I didn't try with those versions before. 🙈

Not it fails in my local env with a more related error: Error: write EBADF.

[luisherranz]

It doesn't seem specific to this particular PR because I just pushed to this other one and it also failed: #836

[DAreRodz]

It doesn't seem specific to this particular PR because I just pushed to this other one and it also failed: #836

I've created a PR that seems to fix the issue: #843