Support for Remix
See original GitHub issueHi 👋,
Supporting frameworks like Next, Nuxt etc is really great. Is there support coming for Remix as well?
Currently, going through the latest release, is this something that we can do having a custom
framework setup?
Thanks in advance.
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
Remix Help Center
Remix Help Center. Go to Remix. Advice and answers from the Remix Team. Frequently Asked Questions. Can I do ____ in Remix? How...
Read more >Community Support — Remix - Ethereum IDE 1 documentation
That is why we created a community support channel where we and other users try to answer your questions if you get stuck...
Read more >Browser Support - Remix
However, thanks to first-class support for Progressive Enhancement, Remix apps can support browsers as old as Netscape 1.0! This works because Remix is...
Read more >Support Remix · Issue #8019 · nrwl/nx - GitHub
Description Instead of Next.js, I want to be able to use Remix Motivation Now that Remix is released, ... Support Remix #8019.
Read more >Remix - Ethereum IDE & community
Remix IDE, is a no-setup tool with a GUI for developing smart contracts. ... We also support teams who build plugins to allow...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s the docs on the custom integration https://firebase.google.com/docs/hosting/express
We’re looking into other frameworks but have no timelines to share. In the meantime we offer two DIY integrations: Vite and Express/custom.
Vite should “just work” out of box (non-SSR ATM.)
With the express/custom integration we call
npm run build
for you, we look for adirectories.serve
field in your package.json telling us where the static content is after build, and then it will look for an optional express app factory (export app = () => { return yourExpressApp }
) or a URL handler function (export handle = (req, res) => { ... }
) exported from your main entry. If the latter is found we’ll treat the app as SSR. We be doing work to document all this better in the next few weeks.