lscripts 1.4.1 → 1.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +12 -4
  2. package/lscripts.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -6,14 +6,15 @@ Command to list all the scripts in your `package.json`. Pick easely wich one you
6
6
 
7
7
  ## Install
8
8
 
9
- With your favourite package manager you can install the package globaly using the git repo web URL.
9
+ Install the lscripts globally using your package manager you like.
10
10
 
11
11
  ``` bash
12
12
  # using npm
13
13
  npm install -g lscripts
14
-
15
14
  # using yarn
16
15
  yarn global add lscripts
16
+ # using pnpm
17
+ pnpm add -g lscripts
17
18
  ```
18
19
 
19
20
  ## Use
@@ -23,5 +24,12 @@ Simply run:
23
24
  lscripts
24
25
  ```
25
26
 
26
- You can then pick the script you want to copy to your clipboard using `Up` or `Down` keyes or by searching for the name of the script or the command its supposed to run and pressing `Enter`.
27
- The script you chose will then be ran using your package manager. It determines the package manager you are using checking if you have a `package-lock` or a `yarn-lock` file in your project to copy the proper command to your clipboard.
27
+ You can then pick the script you want to run using `Up` or `Down` keyes or by searching for the name of the script or the command its supposed to run and pressing `Enter`.
28
+
29
+ The script you chose will then be ran using your package manager. It determines the package manager you are using by checking what kind of lock file is present in your project. For now lscripts is compatible with `npm`, `yarn` and `pnpm`.
30
+
31
+ ## Opitonal flags
32
+
33
+ - `--copy, -c`: This flag allows you to copy the script you pick to your clipboard instead of letting lscripts running it directly for you.
34
+ - `--version -v`: Displays the version of the package you are using.
35
+ - `--help -h`: Displays a help message.
package/lscripts.js CHANGED
@@ -92,7 +92,7 @@ const scripts = getScriptsFromPackageJson(packageJson)
92
92
  const runner = getPackageManagerEngine()
93
93
 
94
94
  if (!runner) {
95
- console.log('Please install your dependencies before using lscripts.')
95
+ console.log('Please install your dependencies at least once before using lscripts.')
96
96
  console.log('lscripts uses the lock file to determine which package manager you are using.')
97
97
  console.log('lscripts is currently only compatible with npm, yarn and pnpm.')
98
98
  exit(1)
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "type": "module",
3
3
  "name": "lscripts",
4
- "version": "1.4.1",
4
+ "version": "1.4.2",
5
5
  "description": "lscripts is a command tool that allows you to list and choose a script from your package.json easely.",
6
6
  "main": "lscripts.js",
7
7
  "bin": {