Skip to content
This repository has been archived by the owner on May 3, 2024. It is now read-only.

Multiple errors displaying in browser console #74

Closed
rohantarai opened this issue Mar 17, 2020 · 4 comments · Fixed by #126
Closed

Multiple errors displaying in browser console #74

rohantarai opened this issue Mar 17, 2020 · 4 comments · Fixed by #126

Comments

@rohantarai
Copy link

🐞 Bug Report

Describe the bug

my module was running and i opened http://localhost:3000 and it worked but then i opened chrome dev tools and i found errors in console.

To Reproduce

it can be reproduced by:

  1. creating a new module
  2. serving it with one-app
  3. running one-app
  4. visiting http://localhost:3000
  5. opening chrome dev tools then console tab

Expected behavior

multiple errors are being displayed in browser console.

Screenshots

chrome console errors

System information

  • OS: Windows
  • Browser (if applies): chrome v80
  • Version of one-app: 5.0.0
  • Node version: 12.16.1
  • Are you using building one-app from source or using the release Docker image? -from source
  • Hosting platform for one-app server: localhost
  • Hosting platform/CDN for your one-app modules: localhost

Additional context

NA

@JamesSingleton
Copy link
Contributor

JamesSingleton commented Mar 17, 2020

@rohantarai,

That first error you are getting is due to the font url not being added to the CSP. https://github.com/americanexpress/one-app/blob/master/docs/api/modules/App-Configuration.md#csp goes over how to create a CSP. You will have to restart the server after adding the CSP changes for them to picked up.

@rohantarai
Copy link
Author

Ok i solved two issues which were caused due to chrome extensions. now i left with other two issues related to reactjs. i hope this will be fixed in upcoming version.

Capture

@JamesSingleton
Copy link
Contributor

@rohantarai,

This is due to @americanexpress/one-app-router using those lifecycle methods and one-app running in strict mode.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants