next-Payload-Serverless-Demo

.smalltalkman2 years ago

10

• 

  jarrod_not_jared

  2 years ago

  @823331358025449502

  to fix this error:

  
  

  "Unknown identifier "handlerConfig" at "config".
  The default config will be used instead."

  
  

  You will need to pull from the next-payload-demo repo, run yarn and then run

  yarn next-payload install

  . There was a fix in

  next-payload

  0.0.21 that fixed this 👍

• 

  jmikrut

  2 years ago

  And -

  @823331358025449502

  the other issue that you've had is now fixed as well 👍

• 

  .smalltalkman2 years ago

  teh message is exactly my trial

  
  

  I get the same error in my browser navigating to localhost:3000/admin

  
  
  

  Unhandled Runtime Error

  
  

  TypeError: tag[primaryAttributeKey].toLowerCase is not a function

  
  
  

  Call Stack

  
  

  eval

  
  

  node_modules\react-helmet\es\Helmet.js (253:0)

  
  

  Array.filter

  
  

  <anonymous>

  
  

  eval

  
  

  node_modules\react-helmet\es\Helmet.js (232:0)

  
  

  Array.reduce

  
  

  <anonymous>

  
  

  getTagsFromPropsList

  
  

  node_modules\react-helmet\es\Helmet.js (229:5)

  
  

  reducePropsToState

  
  

  node_modules\react-helmet\es\Helmet.js (305:0)

  
  

  emitChange

  
  

  node_modules\react-side-effect\lib\index.js (56:0)

  
  

  SideEffect.UNSAFE_componentWillMount

  
  
  

  the cms portion of the other demo works fine

  
  

  Windows, Mongo service, edge and chrome

  
  
  

  one Windows gotcha is non case-sensitive, so what works in Linux might not in Windows
• 

  jessrynkar2 years ago

  I just pulled down a fresh copy of the next-payload-demo and I cannot reproduce this error. Could you send a screenshot of the error when you go to localhost:3000/admin ?

• 

  jarrod_not_jared

  2 years ago

  @854377910689202256

  this is a windows only issue. We should have

  @969226489549713438

  weigh in here 👍

• 

  dribbens

  2 years ago

  Are you on the latest version of next-payload?

  
  https://github.com/payloadcms/next-payload/issues/16
  

  We fixed this last week I believe

• 

  jmikrut

  2 years ago

  yes, this is fixed

• 

  .smalltalkman2 years ago

  I used

  https://github.com/payloadcms/next-payload-demo.git
  
  

  I will try the other

• 

  jmikrut

  2 years ago

  that other package is for installing Payload into

  an existing Next app
  
  

  but you can now re-clone the demo (above) - i just updated the dependency there as well

• 

  .smalltalkman2 years ago

  that's working well thx