Introduce lucid-evolution and wasm compatibility to the frontend #64
Conversation
| import { Blockfrost, CML, Lucid, LucidEvolution, TxSigned, walletFromSeed } from "@lucid-evolution/lucid"; | ||
|
|
||
| export async function makeLucid() { | ||
| const API_KEY = process.env.NEXT_PUBLIC_BLOCKFROST_API_KEY; |
There was a problem hiding this comment.
Where does this variable come from in the browser?
There was a problem hiding this comment.
The api key is defined in an env.local file, each person will need to set this up on their own local instance or it will need to be defined in I believe the Docker file
There was a problem hiding this comment.
I see, does this mean we have to serve the page with next.js? So we can't have a static page with just HTML+JS+CSS?
There was a problem hiding this comment.
NextJS environment variables are injected at build time and I prefixed them with the NEXT_PUBLIC_ prefix so this would make them accessible on the client side. They will just become static after the build and if you want to switch them out you will need to rebuild everything.
Here's the docs that explain how this works: https://nextjs.org/docs/pages/building-your-application/configuring/environment-variables#loading-environment-variables
|
|
||
|
|
||
| /** @type {import('next').NextConfig} */ | ||
| const nextConfig = { |
There was a problem hiding this comment.
We need a line output = "export" for the docker image (to generate a single static page). This line won't work with the headers bit, so maybe we need two different configs, or look at debug vs production flags?
There was a problem hiding this comment.
I can do that but then it will most likely create conflicts with the rewrites. This is what I get from NextJS when I try to use both the rewrites and the output="export" at the same time. https://nextjs.org/docs/messages/export-no-custom-routes
There was a problem hiding this comment.
In the production build we don't need the rewrites anyway, so we can just switch between two different configs based on the flag
There was a problem hiding this comment.
Should I comment out the rewrites in the commit so that the Nix build works?
There was a problem hiding this comment.
Looks like the tests still failed. Should I merge it or wait for that to pass?
|
The nix build failed because of networking issues. I restarted it so hopefully it will pass now. Then we can merge this PR - it will break the static build for now, but I have some ideas for fixing it, which I'm going to try out tomorrow. |
|
|
||
|
|
||
| /** @type {import('next').NextConfig} */ | ||
| const nextConfig = { |
Add lucid-evolution and wasm support.