Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error building the front-end #1104

Closed
manekenpix opened this issue Jul 12, 2020 · 0 comments · Fixed by #1105
Closed

Error building the front-end #1104

manekenpix opened this issue Jul 12, 2020 · 0 comments · Fixed by #1105
Labels
area: front-end type: bug Something isn't working

Comments

@manekenpix
Copy link
Member

manekenpix commented Jul 12, 2020

What happened:

Merging #1103 broke the frontend. During the building process, this happened:

success open and validate gatsby-configs - 0.054s
success load plugins - 0.828s
success onPreInit - 18.606s
success delete html and css files from previous builds - 0.021s
success initialize cache - 0.010s
success copy gatsby files - 0.037s
success onPreBootstrap - 0.005s
success createSchemaCustomization - 0.009s
success source and transform nodes - 1.774s
success building schema - 0.370s

 ERROR #11321  PLUGIN

"gatsby-node.js" threw an error while running the createPages lifecycle:

Reducers may not dispatch actions.



  Error: Reducers may not dispatch actions.
  
  - redux.js:214 dispatch
    [frontend]/[redux]/lib/redux.js:214:13
  
  - index.js:64 action
    [frontend]/[gatsby]/dist/redux/index.js:64:88
  
  - index.js:14 Object.dispatch
    [frontend]/[redux-thunk]/lib/index.js:14:16
  
  - index.js:45 dispatch
    [frontend]/[gatsby]/[gatsby-cli]/lib/reporter/redux/index.js:45:9
  
  - redux.js:483 Object.createLog
    [frontend]/[redux]/lib/redux.js:483:12
  
  - reporter.js:168 Reporter.warn.text [as warn]
    [frontend]/[gatsby]/[gatsby-cli]/lib/reporter/reporter.js:168:41
  
  - patch-console.js:22 Console.console.warn.args [as warn]
    [frontend]/[gatsby]/[gatsby-cli]/lib/reporter/patch-console.js:22:14
  
  - utils.js:449 Object.warn
    [frontend]/[xstate]/lib/utils.js:449:26
  
  - StateNode.js:1313 
    [frontend]/[xstate]/lib/StateNode.js:1313:29
  
  - Array.map
  
  - StateNode.js:1311 StateNode.formatTransitions
    [frontend]/[xstate]/lib/StateNode.js:1311:18
  
  - StateNode.js:321 StateNode.get [as transitions]
    [frontend]/[xstate]/lib/StateNode.js:321:51
  
  - StateNode.js:296 StateNode.get [as on]
    [frontend]/[xstate]/lib/StateNode.js:296:36
  
  - StateNode.js:230 
    [frontend]/[xstate]/lib/StateNode.js:230:93
  
  - Array.forEach
  
  - StateNode.js:230 StateNode._init
    [frontend]/[xstate]/lib/StateNode.js:230:45
  

failed createPages - 0.088s

I don't think it's directly related to the changes made in #1103 (I'd say it's gatsby).
Check this for possible solutions.

What should have happened:
Telescope should've been able to run after the merge.

How to reproduce it (as precise as possible):
Try to run Telescope using the latest commit.

Anything else we need to know?:
Important
Currently, Telescope uses gatsby 2.20.23. Switching to latest (2.24.2) seems to fix the problem, but it creates a different one (that might be related to telescope, not gatsby).
Trying to run Telescope using gatsby v2.24.2 generates this message:

success open and validate gatsby-configs - 0.073s
success load plugins - 0.766s
success onPreInit - 13.889s
success delete html and css files from previous builds - 0.021s
success initialize cache - 0.008s
success copy gatsby files - 0.030s
success onPreBootstrap - 0.008s
success createSchemaCustomization - 0.018s
success source and transform nodes - 1.862s
success building schema - 0.381s

 ERROR #85901  GRAPHQL

There was an error in your GraphQL query:

Cannot read property 'map' of undefined

File: gatsby-node.js:94:18

not finished createPages - 0.035s

Environment:

  • OS:
  • Browser:
manekenpix added a commit that referenced this issue Aug 2, 2020
Fixes #1104 fix error in building the frontend
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: front-end type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant