thuglabs / create-dapp-solana-nextjs Goto Github PK

In case of failed build vercel will fail to update env with committed code.
As a solution husky can be installed. So on each push husky will try build code to check if it successful .

Alternatively, it can be done with GitHub actions on PR opened / updated.

One of templates can be imported to the project is Candy Machine Mint site by levicook.
https://github.com/exiled-apes/candy-machine-mint

The only important thing to change is to move env variables to the config file, since of Next.JS SSR nature it might be easy to use config this way

• NFT Gallery
• Candy Machine

Hello! Are there any contingencies for the mint page using candy machine v2? The major difference that I can see between v1 and v2 is that v2 no longer has both a candy machine config id and an actual candy machine id, but I don't know how to implement this page in the mint site. Any help would be appreciated - thank you!

When I uploaded this to vercel and went to gallery, it could not load the NFTs and was giving a network error.

When I forked and tried to deploy without making any changes, I got the following error

Error: The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. This is normally caused by a misconfiguration in your project.

Please check the following, and reach out to support if you cannot resolve the problem:

1. If present, be sure your `build` script in "package.json" calls `next build`.  
2. Navigate to your project's settings in the Vercel dashboard, and verify that the "Build Command" is not overridden, or that it calls `next build`.  
3. Navigate to your project's settings in the Vercel dashboard, and verify that the "Output Directory" is not overridden. Note that `next export` does **not** require you change this setting, even if you customize the `next export` output directory. Learn More: https://err.sh/vercel/vercel/now-next-routes-manifest</span>

I had to change the "Output Directory" to "build" in project settings on Vercel dashboard to deploy it successfully. I'm not familiar with next.js ecosystem but I realized this is defined in next.config.js.

If this is something non-standard, can we add this bit to the readme?