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 db543b5465 Merge branch 'master' of https://git.2fi-solutions.com/derek/FPSMS-frontend 2 maanden geleden
public initial commit 6 maanden geleden
src Merge branch 'master' of https://git.2fi-solutions.com/derek/FPSMS-frontend 2 maanden geleden
types Modify Session Type 2 maanden geleden
.env.development [feature] update axios 4 maanden geleden
.env.production [feature] update axios 4 maanden geleden
.eslintrc.json [config] update IDE typescript config 3 maanden geleden
.gitignore tsms to fpsms 6 maanden geleden
.npmrc initial commit 6 maanden geleden
.nvmrc initial commit 6 maanden geleden
README.md update po 3 maanden geleden
next.config.js PWA disabled in development 5 maanden geleden
package-lock.json i18n 2 maanden geleden
package.json [M18 Import Testing] Add import m18 po 2 maanden geleden
postcss.config.js initial commit 6 maanden geleden
tailwind.config.js initial commit 6 maanden geleden
tsconfig.json [config] update IDE typescript config 3 maanden geleden
zip_project.ps1 tsms to fpsms 6 maanden geleden

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