Comments (1)
Using WSL is a good solution if you are able to migrate your project files to within WSL's filesystem (which will require running yarn install
again, since some project dependencies download for the specific OS). Eg. Using git clone
straight from WSL, in a directory other than /mnt/c
. When the project files are on Windows (visible to WSL through the mount), build and deploy time within WSL is incredibly slow (45+ min). This is a known file access issue in WSL2 with the 9P protocol (see issue here).
For anyone that has come here looking for a workaround: we've found it best to use Github Actions to build and deploy, as part of CI/CD, even for development/staging environments. It takes only a few minutes at most, particularly if caching is used. We develop locally on Windows just using next dev
, which just spins up a simple Next.js web server, which is sufficient for web layout, components, etc. Development of the SST side is a bit more tedious (requires a git commit
and git push
on each change), but given how much faster deployment is on Github Actions, is worth it.
from open-next.
Related Issues (20)
- Redirect to different domain result in invalid url HOT 1
- ImageFunction fails with "TypeError: Cannot read properties of undefined (reading 'getStore')" HOT 3
- Next config redirects is not working correctly on Next 12 HOT 1
- URL with semicolon in query params throws 400 error HOT 1
- Open next with SST on AWS - Missing Cloudfront Behaviors HOT 7
- Next config redirects is not working correctly with i18n default platform HOT 4
- NX Monorepo support HOT 1
- Post Deployment MIME Type Mismatch With Safari HOT 3
- Re-enable nextjs compression or allow enabling it optionally HOT 12
- Problem using deployed server-function from open-next when using basePath HOT 10
- publishing to v3 tag for use with sst ion HOT 2
- [Feature Request] - package agnostic runner HOT 1
- Missing polyfill for middleware: URLPattern
- Middleware not running for cached responses which should be protected HOT 1
- v3.0.8 might break nextjs 14 (14.1.4) middleware HOT 1
- OpenNext Ignores force-cache Option on fetch Requests (Data Cache Behavior Differs from Vercel) HOT 22
- RSC requests fail because of `.rsc` suffix when using a proxy HOT 2
- Potential Bug in OpenNext Cache Adapter or Incorrect CloudFront Cache Invalidation Examples in the Docs HOT 8
- nextUrl.locale is not updated with pathname locale in middleware
- API routes in NextJS don't return any data 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 open-next.