youwen5/eexiv
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

style: format

Browse source
This commit is contained in:
couscousdude 2024-02-20 07:08:01 +00:00 committed by Team 1280 Programming Laptop
parent d2577dd4ba
commit 38032e1c7f
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -21,6 +21,7 @@ eeXiv borrows from a pioneer in digital open access, arXiv.org, and hosts the mo
[^1]: Whichever idiot decided "arXiv" should be pronounced like "archive" can cope; eeXiv is not changing its name or pronunciation. [^1]: Whichever idiot decided "arXiv" should be pronounced like "archive" can cope; eeXiv is not changing its name or pronunciation.
--- ---
<!-- Copilot --> <!-- Copilot -->
<table> <table>
<img alt="GitHub Copilot" align="left" src="https://raw.githubusercontent.com/KatsuteDev/kdevbot/main/assets/copilot-dark.png#gh-dark-mode-only" width="50"> <img alt="GitHub Copilot" align="left" src="https://raw.githubusercontent.com/KatsuteDev/kdevbot/main/assets/copilot-dark.png#gh-dark-mode-only" width="50">
@ -58,4 +59,3 @@ The dummies guide to maintaining a Next.js project:
- **Footnote**: why don't I have to use the utilities in [`db/loaders.ts`](./src/app/db/loaders.ts) to asynchronously load the data in server side components? - **Footnote**: why don't I have to use the utilities in [`db/loaders.ts`](./src/app/db/loaders.ts) to asynchronously load the data in server side components?
- Next.js will automatically pre-render all server side components into static HTML, which means there will be no performance impact (and in fact performance gain at build time) - Next.js will automatically pre-render all server side components into static HTML, which means there will be no performance impact (and in fact performance gain at build time)
to loading the entire objects into memory. to loading the entire objects into memory.