tyroprogrammer / learn-react-app Goto Github PK

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\simon\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build:markdown' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild:markdown', 'build:markdown', 'postbuild:markdown' ]
5 info lifecycle [email protected]prebuild:markdown: [email protected]
6 info lifecycle [email protected]build:markdown: [email protected]
7 verbose lifecycle [email protected]build:markdown: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]build:markdown: PATH: C:\Users\simon\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\simon\Repos\learn-react-app\node_modules.bin;C:\Users\simon\Repos\learn-react-app\node_modules.bin;C:\Users\simon\AppData\Local\Yarn\Data\link\node_modules.bin;C:\Users\simon\Repos\learn-react-app\node_modules.bin;C:\Users\simon\AppData\Local\Yarn\Data\link\node_modules.bin;C:\Program Files\libexec\lib\node_modules\npm\bin\node-gyp-bin;C:\Program Files\lib\node_modules\npm\bin\node-gyp-bin;C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Program Files\nodejs;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Java\jdk1.8.0_172\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\nodejs;C:\Program Files\Git\cmd;C:\Gradle\gradle-4.7\bin;C:\Program Files (x86)\Yarn\bin;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Microsoft VS Code\bin;C:\Users\simon\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\simon\AppData\Roaming\npm;C:\Users\simon\AppData\Local\Yarn\bin;C:\Program Files\heroku\bin;C:\src\flutter_windows_v1.0.0-stable\flutter\bin;
9 verbose lifecycle [email protected]build:markdown: CWD: C:\Users\simon\Repos\learn-react-app
10 silly lifecycle [email protected]build:markdown: Args: [ '/d /s /c', 'node scripts/processMarkdown' ]
11 silly lifecycle [email protected]build:markdown: Returned: code: 1 signal: null
12 info lifecycle [email protected]build:markdown: Failed to exec build:markdown script
13 verbose stack Error: [email protected] build:markdown: node scripts/processMarkdown
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\simon\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:304:16)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at EventEmitter.emit (events.js:191:7)
13 verbose stack at ChildProcess. (C:\Users\simon\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at ChildProcess.emit (events.js:191:7)
13 verbose stack at maybeClose (internal/child_process.js:920:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\simon\Repos\learn-react-app
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\simon\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "build:markdown"
18 verbose node v6.11.4
19 verbose npm v6.1.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] build:markdown: node scripts/processMarkdown
22 error Exit status 1
23 error Failed at the [email protected] build:markdown script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

In Section: Handling Events
http://localhost:3000/tutorial/handling-events

The first example creates a function that contains a button
"function ClickableButton(props){ ..."
The second example creates a function that contains an InputBox
but it still uses the name ClickableButton

Although this is not an error, using the second function name confused me since I thought the two examples were talking about the same thing until I cut and pasted them to do a quick comparison.
recommended solution: Changing the second name to function "ChangeableInput" would reduce the confusion.

BTW: excellent tutorial. thank you.

First time playing seriously with React, thanks for the tutorial!

Just one thing: I was looking through the React documentation and found that the lifecycle function componentWillMount() is being deprecated. You may want to address this in chapter 6 if you think it's within the scope of the tutorial.

I suggest deleting the link to gitpod if this issue is not planned to be fixed any time soon.

Can you please add an example where we connect to an actual working API? Would be great to see how to manage APIs keys, constants, etc.

The use of render props is misguided in the Card example. Render props allow a parent component to provide data to a render without having to explicitly know what its children are. If a render prop takes no arguments it should just be swapped out for static JSX.

Hey there, the repo description says "guided as well as guided". Can't PR that so here's just an issue FYI.

First off, thanks for this tutorial, it's very nice!

I noticed in doing exercise/06-LifecycleMethod that the data is not loading.

Proxy error: Could not proxy request /api/company/profile/AMZN from 172.17.0.3:3000 to https://financialmodelingprep.com.
See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNRESET).
Proxy error: Could not proxy request /api/company/profile/AMZN from 172.17.0.3:3000 to https://financialmodelingprep.com.
See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (EAI_AGAIN).

I tried changing API_BASE to const API_BASE = https://financialmodelingprep.com/api/company/profile`;` but then the browser wouldn't load it due to financialmodelingprep.com

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://financialmodelingprep.com/api/company/profile/AMZN. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

I suggest simplifying the tutorial so that the data is served by the tutorial instead of going to a 3rd party resource.

node:events:491
throw er; // Unhandled 'error' event
^

Error: spawn cmd ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn cmd',
path: 'cmd',
spawnargs: [ '/s', '/c', 'start', '""', '/b', '"http://localhost:3000/"' ]
}

Node.js v18.13.0

npm-run-all would work also for users using yarn who don't have npm installed.

deleted comments

run npm install or yarn install