Comments (4)
timneutkens
commented on April 28, 2024
2
@matthewmueller can this be closed in favor of _document.js?
from next.js.
davedbase
commented on April 28, 2024
I've also been experimenting with representing the whole DOM in memory and rendering on page load for the better part of a year. Seeing some pretty incredible speed and performance as a result. This is definitely the right direction and you guys have done some stellar work so far!
We originally tied our solution to React but moved away to make it more framework agnostic (that being difficult because of the JSX dependency). Matter of fact our project is called Nex, very similar to Next.js but a solving a slightly different problem.
Kudos for a fantastic initial release.
from next.js.
mmmeff
commented on April 28, 2024
This is related to both #50 and #75 in that there's a need for control of the entire html document, not just the <head>
from next.js.
timneutkens
commented on April 28, 2024
Closing. If needed you can re-open ❤️
from next.js.
Related Issues (20)
- Firebase hosting w/ monorepo - "Error: > Couldn't find a 'pages' directory..." HOT 1
- Static Analysis does not take conditional logic into account as to whether a Node API will be used at runtime on the edge HOT 1
- `DYNAMIC_SERVER_USAGE` error being thrown when combining `not-found` and the old `404` pages HOT 6
- File conventions are applied inside private folders
- Turbopack: CommonJS require import of 'canvas' fails to resolve when using react-pdf library HOT 1
- Set multiple cookies on API routes (Pages Router) HOT 1
- HMR broken for runtime edge when using "use client" directive
- Discrepancy in searchParams between server and client after clicking `Link` HOT 1
- Dev server is taking too much memory in my Macbook & Windows machine HOT 1
- Dev server is taking too much memory in my Macbook & Windows machine HOT 3
- 创建新的next14项目中，产生了一个错误 HOT 1
- 创建hello word,出现未知错误 HOT 1
- 构建项目出现问题 HOT 4
- npm run build element type is invalid expected a string (for built-in components) or a class/function HOT 1
- npm run build element type is invalid expected a string (for built-in components) or a class/function HOT 1
- npm run build element type is invalid expected a string (for built-in components) or a class/function
- Docs: Allow https://nextjs.org/ to work when PerformanceObserver is undefined
- Memory Leak with Next.js's global fetch. Tested against http module HOT 18
- Missing styles on not-found (404) page HOT 1
- > Build error occurred HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next.js.