Skip to content

Conversation

@dario-piotrowicz
Copy link
Contributor

@dario-piotrowicz dario-piotrowicz commented Jan 13, 2025

As per opennextjs/opennextjs-cloudflare#236 (comment)

Note

Maybe the warning could go in the OpenNext overview page itself?

I considered that but I am not sure if we should put such a warning front and center (as one of the first things devs would see).
Maybe it's better to just duplicate the warning for now and then reconsolidate it when/if we decide to restructure the docs to better document the shared aspects of the adapters?

Copy link
Contributor

@vicb vicb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

Copy link
Contributor

@conico974 conico974 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a little comment, other than that LGTM

@dario-piotrowicz dario-piotrowicz merged commit e188122 into opennextjs:main Jan 13, 2025
1 check passed
@dario-piotrowicz dario-piotrowicz deleted the dario/windows-support-warnings branch January 13, 2025 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants