-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
add Rspack section in Hot reload documentation #2896
Comments
Personally, instead of adding a section, I would add a notice with a link to the Or add something like this in the section regarding hot-reload:
|
that sounds good to me |
@hardfist do you want to create a PR for this issue ? |
yes |
It looks like the link provided (https://www.rspack.dev/guide/nestjs.html) is no longer available. Do you know if the content has been moved to a different location? Also, I’m finding the current guide (https://rspack.org/guide/tech/nestjs) a bit challenging for newcomers like me who just started using rspack. Could you recommend any other resources or documentation that might be more beginner-friendly, particularly for integrating Rspack with NestJS? Thanks! |
https://rspack.dev/guide/tech/nestjs it's moved here |
I also opened an issue recently there: rspack-contrib/rspack-examples#110. Do you think having some knowledge of Webpack or similar tools is necessary for this integration? I come from a backend background, and I'm finding it a bit difficult to follow the docs. |
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
We(Rspack team) receives lots of issues and questions about how to use Rspack bundle Nest application and support Hot Reload, even we have a section about Nest in our website(https://www.rspack.dev/guide/nestjs.html), I think it maybe helpful Nest documentation have a Rspack section about it too.
Describe the solution you'd like
add a Rspack section in Nest documentation
Teachability, documentation, adoption, migration strategy
similar to current webpack section
What is the motivation / use case for changing the behavior?
No Change
The text was updated successfully, but these errors were encountered: