Error after upgrading @frontity/wp-source to 1.5.0

Bug report

• I’ve searched for existing issues
• I’ve checked documentation: https://docs.frontity.org
• I’ve checked community forum: https://community.frontity.org

Describe the expected behavior getting the data from source as expected

Describe the observed behavior strange error appears in the console when navigating to any page

TypeError: Cannot read property 'func' of null
    at eval (actions.ts?f1c8:46)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (actions.ts:6)
    at _next (actions.ts:6)
    at eval (actions.ts:6)
    at new Promise (<anonymous>)
    at eval (actions.ts:6)
    at eval (actions.ts?f1c8:12)
    at Object.eval [as fetch] (create-store.js?81b0:27)
    at eval (actions.ts?fe69:18)

Describe the steps involved to reproduce the problem upgrade the wp-source by running this command npm install @frontity/wp-source@latest

Add info about your system

System:

• OS: Windows 10 10.0.18362
• CPU: (8) x64 Intel® Core™ i7-7700HQ CPU @ 2.80GHz
• Memory: 2.72 GB / 15.89 GB

Binaries:

• Node: 12.13.1 - C:\Program Files\nodejs\node.EXE
• npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD

Browsers:

• Edge: 44.18362.449.0
• Internet Explorer: 11.0.18362.1

npmPackages:

• bootstrap: ^4.4.1 => 4.4.1
• frontity: ^1.4.4 => 1.4.4
• prop-types: ^15.7.2 => 15.7.2
• react: ^16.12.0 => 16.12.0
• react-slick: ^0.25.2 => 0.25.2
• react-spinners: ^0.7.2 => 0.7.2
• react-spring: ^8.0.27 => 8.0.27
• slick-carousel: ^1.8.1 => 1.8.1

npmGlobalPackages:

• frontity: Not Found
• npx: Not Found

it was working will before updating to 1.5.0 to use REST API - Head Tags

[SantosGuillamot]

Not sure if it’ll help in this case, but I had a similar problem and it was solved after deleting node_modules and the package-lock.json, and running npm install at the root again as explained here. If you haven’t done it yet, I guess it’d be a good idea to try this.

[SantosGuillamot]

Can you please take a look at our automations?

Sure, I guess that if a done issue is reopened it should go back to the to-do column, not to in-progress.

@SantosGuillamot my opinion is that we should fix this in this sprint because it is forcing people to remove node_modules and the package-lock.json each time they update Frontity.

Yes, I agree that if this is happening on every update, and it’s “breaking” Frontity, it should be fixed.