We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, thanks for this great package.
I'm experimenting with a few potential improvements using macros.
Would it be useful to add a few steps in the readme describing how to integrate Rackt with RacketScript and deploy a Rackt app?
(I had to manually edit some compiled files to properly point to rackt.rkt.js, depending on where I installed the pkg)
rackt.rkt.js
Also, I noticed the example page uses vite. Is this the standard way to load React? (Sorry, I'm a newb at frontend development)
Thanks again for creating this!
The text was updated successfully, but these errors were encountered:
@stchang sorry for not answering (I had some issues). Yes, of course. I'll improve the readme.
Also, I noticed the example page uses vite. Is this the standard way to load React?
It's not the standard, it's just an alternative to webpack. I'll explain why I used vite instead of webpack in the readme as well
Sorry, something went wrong.
No branches or pull requests
Hi, thanks for this great package.
I'm experimenting with a few potential improvements using macros.
Would it be useful to add a few steps in the readme describing how to integrate Rackt with RacketScript and deploy a Rackt app?
(I had to manually edit some compiled files to properly point to
rackt.rkt.js
, depending on where I installed the pkg)Also, I noticed the example page uses vite. Is this the standard way to load React? (Sorry, I'm a newb at frontend development)
Thanks again for creating this!
The text was updated successfully, but these errors were encountered: