fix: links to images (#30990)
Images that used the inline link format do not show up on Docusaurus or the old website infrastructure. There are only 2 guides using it so it is faster to change the format rather than figuring out why the parsin logic does not work. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ref: https://github.com/electron/electronjs.org-new/issues/84
This commit is contained in:
parent
64c70c420f
commit
4576d9d23e
2 changed files with 5 additions and 11 deletions
|
@ -120,9 +120,9 @@ file in the directory you executed it in. Both files can be analyzed using
|
|||
the Chrome Developer Tools, using the `Performance` and `Memory` tabs
|
||||
respectively.
|
||||
|
||||
![Performance CPU Profile][performance-cpu-prof]
|
||||

|
||||
|
||||
![Performance Heap Memory Profile][performance-heap-prof]
|
||||

|
||||
|
||||
In this example, on the author's machine, we saw that loading `request` took
|
||||
almost half a second, whereas `node-fetch` took dramatically less memory
|
||||
|
@ -412,8 +412,6 @@ As of writing this article, the popular choices include [Webpack][webpack],
|
|||
[Parcel][parcel], and [rollup.js][rollup].
|
||||
|
||||
[security]: ./security.md
|
||||
[performance-cpu-prof]: ../images/performance-cpu-prof.png
|
||||
[performance-heap-prof]: ../images/performance-heap-prof.png
|
||||
[chrome-devtools-tutorial]: https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/
|
||||
[worker-threads]: https://nodejs.org/api/worker_threads.html
|
||||
[web-workers]: https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue