Package.json updates: Windows & yarn #240
3 changed files with 7469 additions and 4 deletions
17
README.md
17
README.md
|
@ -32,8 +32,21 @@
|
||||||
- **This repo will not run locally if you do not also have the LBRY app/daemon and the [web-daemon](https://github.com/lbryio/web-daemon) running.**
|
- **This repo will not run locally if you do not also have the LBRY app/daemon and the [web-daemon](https://github.com/lbryio/web-daemon) running.**
|
||||||
- When running locally and completing the tipping example in Playground, the LBC donated to a creator comes from _your_ LBC balance. Otherwise, the example will fail. On production, the donated LBC comes from LBRY.
|
- When running locally and completing the tipping example in Playground, the LBC donated to a creator comes from _your_ LBC balance. Otherwise, the example will fail. On production, the donated LBC comes from LBRY.
|
||||||
|
|
||||||
## Installation
|
## Local Installation
|
||||||
`npm i`
|
|
||||||
|
### npm
|
||||||
|
```bash
|
||||||
|
npm install
|
||||||
|
```
|
||||||
|
|
||||||
|
### Yarn
|
||||||
|
|
||||||
|
There is a yarn.lock file, you can thus use yarn to install a guaranteed working configuration of packages. This is generally a lot faster to install and more stable. Yarn as a CLI is not necessarily more stable than npm and as such, it's optional. Install yarn here: https://yarnpkg.com/en/docs/install
|
||||||
|
|
||||||
|
Then
|
||||||
|
```bash
|
||||||
|
yarn install
|
||||||
|
```
|
||||||
|
|
||||||
## Development
|
## Development
|
||||||
`npm run watch` and visit [localhost:8080](http://localhost:8080)
|
`npm run watch` and visit [localhost:8080](http://localhost:8080)
|
||||||
|
|
|
@ -69,7 +69,7 @@
|
||||||
"updates": "^6.2.1"
|
"updates": "^6.2.1"
|
||||||
},
|
},
|
||||||
"engines": {
|
"engines": {
|
||||||
"node": "10.2.x"
|
"node": ">=10.2 <10.15.1"
|
||||||
},
|
},
|
||||||
For regular users using npm this is just an indicator on which versions of node that can run this project fine. Not really an important change, want me to revert it? For regular users using npm this is just an indicator on which versions of node that can run this project fine.
If you use an alternative dependency manager, like Yarn, you'll get an error if your node version doesn't match the ones listed under "engines".
My change only extends the list of working node versions to include the versions of node between the last set version(10.2.x) and the latest recommended version listed on https://nodejs.org/en/ (which I use and it works without problems).
Not really an important change, want me to revert it?
No it's fine, since yarn is being added anyway. No it's fine, since yarn is being added anyway.
|
|||||||
"husky": {
|
"husky": {
|
||||||
"hooks": {
|
"hooks": {
|
||||||
|
@ -81,7 +81,7 @@
|
||||||
"private": true,
|
"private": true,
|
||||||
"scripts": {
|
"scripts": {
|
||||||
"css": "sass --load-path=node_modules --update app/sass:app/dist --style compressed",
|
"css": "sass --load-path=node_modules --update app/sass:app/dist --style compressed",
|
||||||
"format": "eslint '**/*.js' --fix --ignore-pattern '/app/dist/'",
|
"format": "eslint \"**/*.js\" --fix --ignore-pattern '/app/dist/'",
|
||||||
"start": "npm run css && npm i && NODE_ENV=production node index.js",
|
"start": "npm run css && npm i && NODE_ENV=production node index.js",
|
||||||
"test": "run-s test:*",
|
"test": "run-s test:*",
|
||||||
"test:dependencies": "updates --update ./ --exclude fastify,prismjs",
|
"test:dependencies": "updates --update ./ --exclude fastify,prismjs",
|
||||||
|
|
Loading…
Reference in a new issue
This looks confusing, what does it do?