-
Notifications
You must be signed in to change notification settings - Fork 153
add command to build and run OpenNext locally with dev overrides #853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 3ac2fba The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
e16641a
to
a28f8ce
Compare
@sommeeeer Honestly i'm not sure what to do with this. The only point right now of such a command is for people contributing to OpenNext, and you'll likely end up with your own config (at least to test things out). Best things to do would probably just be to make it work for monorepo, and if we really want to have a |
Yeah the name should not be dev.
Should I continue on this one (im trying to make it work in monorepos) or perhaps close it? This was mainly for people working on OpenNext as it can be a bit cumbersone to copy and make config files each time you need to test something quick locally. Like features in the routingHandler or similar. |
Why not just a command to generate the base "dev" config instead. I feel like this will give us enough |
For #541
I'll open this in draft mode for now. It wont work in a monorepo as of now. Im open for suggestions.