Closed davidrhoderick closed 3 years ago
Hi,
I also noticed this a couple of days ago! I will start to look into it, hopefully someone in the Community have some insights. And thanks for the kind words. 😄
I noticed that the Span and HiddenInput processors used export default connect(), while the other processors only used export default. So I removed the connect, and it started to work again.
After the change, the package does not work at all. I believe it is a bug in the Frontity html2react package. I have reported it to the community here.
The package works now! 👍
Great job on reviving and finishing this plugin from the earlier version.
I had a problem with a deployment today because of a new package I added (
color
) and ranrm -rf node_modules && rm -rf package-lock.json && rm -rf yarn-error.log && rm -rf yarn.lock && npm cache clean --force
thennpm install
, which upgraded a couple packages (e.g., Frontity went to version 15).Right after that, I brought up the site with
npx frontity dev
and got the following error:I don't really understand what's going on there and I found that if I comment out
cf7HiddenInputs.js
, I also get the error oncf7Span.js
. If I comment out both those imports and remove them from the libraries, I don't get the error. Unfortunately, I can't confirm that the package works without those elements because the site I'm using it on is having other issues as per this post.