-
Notifications
You must be signed in to change notification settings - Fork 465
Custom directives for NextJs 13 #5840
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
Milestone
Comments
@mununki I'd like to know if it this can be achievable via ppx kind of userland apporoach |
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
cristianoc
added a commit
that referenced
this issue
Feb 10, 2023
Allow to specify directives emitted verbatim at the top of generated js files. See #5840
In upcoming 10.1.3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NextJs 13 introduces a new
app
directory for utilizing server components. Client components imported by a server component must have a"use client";
directive similar to strict mode. Usingraw
doesn't work because the directive must be above all code/imports.Here are some ideas I thought of:
And since so many files will have the same name, #4874 would also help with a big pain point of using NextJs w/ ReScript.
The text was updated successfully, but these errors were encountered: