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.
 
 
CANCERYS\kw093 8421e66ec4 update пре 3 дана
.cursor changed the look and feel slightly пре 3 недеља
public logo update пре 5 месеци
src update пре 3 дана
types eslint suggested spacing пре 8 месеци
.env.development [feature] update axios пре 10 месеци
.env.production no message пре 1 недеља
.eslintrc.json [config] update IDE typescript config пре 10 месеци
.gitignore tsms to fpsms пре 1 година
.npmrc initial commit пре 1 година
.nvmrc initial commit пре 1 година
README.md update po пре 9 месеци
check-translations.js update пре 4 месеци
next.config.js Please check the follow files, i comment the warning part for deployment, пре 8 месеци
package-lock.json no message пре 1 недеља
package.json no message пре 1 недеља
postcss.config.js eslint suggested spacing пре 8 месеци
tailwind.config.js no message пре 3 недеља
tsconfig.json Fix the files that make project failed to compile пре 3 недеља
zip_project.ps1 the zip file ignore the .env.development to make logout go to 10.100.0.81:3000 temperately пре 3 месеци

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).