frigadehq / frigade-react-nextjs-demo

A demo app that shows how to use Frigade with React + Next.js

Frigade React + Next.js Example

This is a simple example of how to use Frigade with React and Next.js.

Getting Started

Install dependencies:

yarn

Then run the local development server (make sure to trust the local certificate for https):

yarn dev

frigade-react-nextjs-demo's Issues

Request to include config.yaml in git repo

Hi there,

I am just learning about Frigade and am trying to understand how the frontend interacts with the service. It could be helpful to include the config.yaml in the git repo so that developers can reference it when understanding the flows.

Thanks

Incompatible script command for opening the browser.

The current script command: "open-browser": "open https://localhost:5678" is not a standard command on Windows or Linux.

I believe it's necessary to make sure the script command is compatible across different OS so that developers can have a smooth experience and focus on solving problems.

I came up with two solutions
. One is to make it a single line command like this: "open-browser": "node -e \"const { execFile } = require('child_process'); /^win/.test(process.platform) ? execFile('cmd', ['/c', 'start', 'https://localhost:5678']) : execFile('xdg-open', ['https://localhost:5678'])\"", which makes it harder to read.

Another solution would be to add a function like this in server.js:

const { execFile } = require('child_process');

function openBrowser(url) { if (/^win/.test(process.platform)) { execFile('cmd', ['/c', 'start', url]); } else { execFile('xdg-open', [url]); } }

openBrowser('https://localhost:5678');,

and then just run the script like this: "dev": "yarn node server.js", which makes it more maintainable and readable.