React Create a Simple JSX Element

React Create a Simple JSX Element
0

I think some people have problems with this sometimes but I keep getting

Uncaught ReferenceError: React is not defined

Every time I try to start this lesson. Here is what chrome says:

A cookie associated with a cross-site resource at http://doubleclick.net/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
create-a-simple-jsx-element:1 A cookie associated with a cross-site resource at https://doubleclick.net/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
frame.js:144 Refused to load the script ‘https://unpkg.com/[email protected]/umd/react.production.min.js’ because it violates the following Content Security Policy directive: “script-src ‘self’ ‘unsafe-eval’ ‘unsafe-inline’ https://www.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://js.stripe.com”. Note that ‘script-src-elem’ was not explicitly set, so ‘script-src’ is used as a fallback.

At @ frame.js:144
create-a-simple-jsx-element:1 Refused to load the script ‘https://unpkg.com/[email protected]/umd/react-dom.production.min.js’ because it violates the following Content Security Policy directive: “script-src ‘self’ ‘unsafe-eval’ ‘unsafe-inline’ https://www.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://js.stripe.com”. Note that ‘script-src-elem’ was not explicitly set, so ‘script-src’ is used as a fallback.

frame.js:91 Uncaught ReferenceError: React is not defined
create-a-simple-jsx-element:1 A cookie associated with a cross-site resource at https://m.stripe.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
198DBWrapper.mjs:206 Uncaught (in promise) DOMException: Failed to execute ‘transaction’ on ‘IDBDatabase’: The database connection is closing.
at https://www.freecodecamp.org/forum/javascripts/workbox/workbox-core.prod.js:1:3581
at new Promise ()
at x.transaction (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-core.prod.js:1:3546)
at async x.u (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-core.prod.js:1:3700)
at async x.put (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-core.prod.js:1:4133)
at async o.setTimestamp (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-expiration.prod.js:1:562)
at async updateTimestamp (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-expiration.prod.js:1:1532)
at async Object.cacheDidUpdate (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-expiration.prod.js:1:2563)
at async Object.put (https://www.freecodecamp.org/forum/javascripts/workbox/workbox-core.prod.js:1:2191)
(anonymous) @ DBWrapper.mjs:206
transaction @ DBWrapper.mjs:205

Thanks for any help,

I believe there is a bug in freeCodeCamp right now. All the exercises related to react are broken because of this. Everything is getting “Uncaught reference error”. Seems like it may be due to a cross-site security issue.

I have also experienced this issue. I agree with gnuhenry, it must be a bug in freeCodeCamp.

at this time freecodecamp works reliably only on google chrome