fix: Move to yarn
npm wasn't dealing well with large numbers of dependencies, and the updating process is a bit clunky (requires me to delete the node_modules directory each time). Trying yarn for now
This commit is contained in:
parent
ba84377eae
commit
2518707d6a
2
.gitignore
vendored
2
.gitignore
vendored
|
@ -31,7 +31,7 @@ yarn-error.log*
|
|||
|
||||
# yarn vs npm conflict
|
||||
package-lock.json ## use yarn.lock instead
|
||||
yarn.lock
|
||||
# yarn.lock
|
||||
|
||||
# Local Netlify folder
|
||||
.netlify
|
||||
|
|
|
@ -91,3 +91,4 @@ Overall, the services which we use are:
|
|||
|
||||
- Commits follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary)
|
||||
- For elicit and metaculus, this library currently filters out questions with <10 predictions.
|
||||
- The database is updated once a day, at 3:00 AM UTC, with the command `ts-node -T src/backend/flow/doEverythingForScheduler.ts`. The frontpage is updated after that, at 6:00 AM UTC with the command `ts-node -T src/backend/index.ts frontpage`. It's possible that either of these two operations makes the webpage briefly go down.
|
||||
|
|
22890
package-lock.json
generated
22890
package-lock.json
generated
File diff suppressed because it is too large
Load Diff
|
@ -7,7 +7,8 @@
|
|||
"url": "git+https://github.com/QURIresearch/metaforecast.git"
|
||||
},
|
||||
"keywords": [
|
||||
"forecasts", "predictions"
|
||||
"forecasts",
|
||||
"predictions"
|
||||
],
|
||||
"author": "Nuño Sempere",
|
||||
"license": "MIT",
|
||||
|
@ -111,6 +112,7 @@
|
|||
"@graphql-codegen/typescript-operations": "^2.5.5",
|
||||
"@svgr/cli": "^6.5.0",
|
||||
"@types/pg": "^8.6.5",
|
||||
"eslint": "^8.25.0"
|
||||
"eslint": "^8.25.0",
|
||||
"eslint-config-next": "^12.3.1"
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue
Block a user