A website to act as a splash page for all things I do. It's hosted on https://msr.codes/
- Next.js 12, for all your production-ready React SSR (or Static) needs
- Google TypeScript Style, for consistent, readable code
- Husky, for pre-commit linting and build checks
- Issue Templates, to get you up and running in Open Source quickly
Run any of the following scripts using yarn:
yarn <script>
| Script | Description |
|---|---|
| build | Build the Next.js application, ready to be ran with start |
| clean | Remove linter output files |
| dev | Start the Next.js application in hot-reloading mode, for development |
| fix | Automatically fix all linting issues in files |
| lint | Check all files, reporting them to the console |
| start | Start the Next.js application in production mode, requires build |
Install it using npm.
npm install --global yarn
Do not push sensitive keys to GitHub. You should follow Next.js' Guide for environment variables.
This includes:
- .env.local: Use a
.env.localfile for any sensitive keys. These should not be pushed to GitHub. - .env: Use a
.envfile for any application configuration that can be safely committed to GitHub, such as aPORTvalue.
By default, Next.js will only load environment variables in the Node.js environment and not load them in the browser.
It may be the case that, in some circumstances, it is necessary to load these values in the browser. To do this, prefix the environment variable with NEXT_PUBLIC_:
NEXT_PUBLIC_ANALYTICS_ID=fooUse this table to store and describe the environment variables used in your application so that others can maintain your application.
| Key | Description | Required |
|---|---|---|
| PORT | The port that the application runs on. | No |
| NEXT_PUBLIC_FOO | An example value. | No |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent