wardubz54
31 May 2021 15:42
1
Hi, I am trying to use the âfrontityâ command in the chrome console, but the response from the console is that the frontity is not defined.
I also have another problem, the console throws me all the time fixRegExpWellKnownSymbolLogic is not a function
I have no idea where the problem may be, the only thing I have done is initialize the project as it says in the guide.
Español:
Buenas, he empezado a usar frontity hoy mismo y me esta dando una serie de errores que no consigo saber resolver, estoy siguiendo un tutorial y veo que usa en la consola de chrome el comando frontity.state.source, comando que yo no puedo usar por que la respuesta es todo el rato âfrontity is not definedâ.
TambiĂ©n tengo otro problema y es que cuando abro la consola siempre tengo un fallo que dice lo siguiente âfixRegExpWellKnownSymbolLogic is not a functionâ este error si que no tengo ni la mas mĂnima idea de donde viene, reciĂ©n instale frontity y no he tocado casi nada.
Si podéis ayudarme os lo agradeceria.
Un saludo
gajorro
1 June 2021 09:36
2
juanma
3 June 2021 09:18
3
Hi @wardubz54 and @gajorro
A fix for this issue has been implemented and it will available in the next release
frontity:master â frontity:changeset-release/master
opened 07:06AM - 03 Jun 21 UTC
This PR was opened by the [Changesets release](https://github.com/changesets/act⊠ion) 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`](https://github.com/frontity/frontity/commit/2f9884270490d1a67c3ba6f061831b24ae4cc038) [#826](https://github.com/frontity/frontity/pull/826) Thanks [@michalczaplinski](https://github.com/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`](https://github.com/frontity/frontity/commit/a154a9cb7093ab0199c01f28b6363f93427abb17) [#840](https://github.com/frontity/frontity/pull/840) Thanks [@luisherranz](https://github.com/luisherranz)! - Fix Webpack/TS-Node excludes not working on Windows.
- [`63154b4f`](https://github.com/frontity/frontity/commit/63154b4fb16095ccf22e4862c6d91c9c6157af67) [#837](https://github.com/frontity/frontity/pull/837) Thanks [@luisherranz](https://github.com/luisherranz)! - Fix transpilation of `frontity.config.js` files in external packages.
juanma
7 June 2021 16:32
4
The latest release fix this issue
Features
As part of the AMP feature , we have made 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. #826
Fixes
Fix Webpack/TS-Node excludes not working on Windows. #840
Fix transpilation of frontity.config.js files in external packages. #837
Refactor createSymlinks to use a custom implementation of fs-extra's readFile function. #843
Credits
Huge thanks to @michâŠ
1 Like