FPSMS-frontend
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
PC-20260115JRSN\Administrator 67ee15b312 no message 4 days ago
.cursor changed the look and feel slightly 3 weeks ago
public logo update 5 months ago
src no message 4 days ago
types eslint suggested spacing 8 months ago
.env.development [feature] update axios 10 months ago
.env.production no message 1 week ago
.eslintrc.json [config] update IDE typescript config 10 months ago
.gitignore tsms to fpsms 1 year ago
.npmrc initial commit 1 year ago
.nvmrc initial commit 1 year ago
README.md update po 9 months ago
check-translations.js update 4 months ago
next.config.js Please check the follow files, i comment the warning part for deployment, 8 months ago
package-lock.json no message 1 week ago
package.json no message 1 week ago
postcss.config.js eslint suggested spacing 8 months ago
tailwind.config.js no message 3 weeks ago
tsconfig.json Fix the files that make project failed to compile 3 weeks ago
zip_project.ps1 the zip file ignore the .env.development to make logout go to 10.100.0.81:3000 temperately 3 months ago

README.md

This is a Next.js project bootstrapped with create-next-app.

Setting Up the Environment

It is recommended to use the same node and npm versions for development. An easy way to do so would be to use nvm (Linux/MacOS, Windows).

Version

nvm: 1.1.12

After installing nvm, run:

nvm use
npm install

This will automatically use the node version defined in .nvmrc and then proceed with installing the necessary dependencies for development.

Getting Started

First, run the development server:

npm run dev

Open http://localhost:3000 with your browser to see the result.

References

This project uses the following libraries:

Qrcode Testing

https://stackoverflow.com/questions/16835421/how-to-allow-chrome-to-access-my-camera-on-localhost Local Qrcode testing require setting tweak Steps:

  1. Navigate to chrome://flags/#unsafely-treat-insecure-origin-as-secure in Chrome.
  2. Find and enable the Insecure origins treated as secure section (see below).
  3. Add any addresses you want to ignore the secure origin policy for. Remember to include the port number too (if required).