You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[NodeJS](https://nodejs.org/en/download/), including `npm` of version 7 or higher (check existing version with `npm -v`, to update an existing nodejs, we can suggest [this guide](https://phoenixnap.com/kb/update-node-js-version).)
63
+
-[Deno](https://deno.com/)
64
64
1. In the GitHub interface, [make a fork][link_fork] of
65
65
https://github.com/bids-standard/bids-validator to your own user (called `USER` for the
66
66
sake of the example)
@@ -71,18 +71,9 @@ To participate, be sure you know how to
71
71
- You will now have a new directory called `bids-validator`
72
72
- navigate to that directory and run `git status` to verify that it's a `git`
73
73
directory
74
-
- run `npm install` to install the BIDS validator
75
-
1. Upon inspection of the `bids-validator` repository we can find the
76
-
"executable" BIDS validator, located in `<...>/bids-validator/bin`, where
77
-
`<...>` is the path to your `bids-validator` repository
78
-
- To make this executable available from the command line, we have to add it
79
-
to the path. On Unix systems with bash as their default shell, this means
80
-
editing the `.bashrc` file by adding the following line to the bottom of
81
-
it: `export PATH="$PATH:<...>/bids-validator/bin"` ... Note that `<...>`
82
-
again needs to be replaced by the path to your BIDS validator repository
83
-
- Now whenever you open a new command line, we will have the `bids-validator`
84
-
executable available. You can verify by opening a new command line and
85
-
typing `bids-validator --version`, and it should print the version number
0 commit comments