Here is the other standard way to do it, to help understand better. It has one test clause, with -o separating the two conditions in the test:
The previous post is also fine, of course. It has two separate test clauses, with || separating the test clauses:
Hello every one,
i am trying to compile c++ modules.
while compiling a module i am getting the following error.
cdbh_RecordStore.C:32:23: error: rw/regexp.h: No such file or directory
make: *** Error 1
I googled for the solution , i found that this is a Rogue wave class.
actually... (0 Replies)
Hi All,
I am using a shell script for SFTPing the files to target server. The problem which I am facing is that even if the files are not transferred, the script finishes successfully. I want the script to fail in case the remote directory does not exists.
The script which I am using is as... (1 Reply)
Hi,
I am installing gcc cross compiler for x86_64.
After installation when i am compiling simple program, i am getting error as
"/usr/cross/lib/gcc-lib/x86_64-pc-elf/3.2.3/../../../../x86_64-pc-elf/bin/ld: cannot open crt0.o: No such file or directory"
Please tell me how to resolve this... (1 Reply)
hi,
I get this error when I compile my source on mac Leopard.
is because I need to configure openGL path ?
Monitor.h:15:60: error: GL/glut.h: No such file or directory
Monitor.h:16:60: error: GL/gl.h: No such file or directory
Monitor.C: In function 'void display2()':
Monitor.C:77:... (0 Replies)
Hi,
I am trying to do scp using the following script:
#!/usr/local/bin/bash
BUILDDATE=20120220
for line in `cat arch_host_plat_src_dest`
do
src=`echo $line | cut -d: -f4`
dest=`echo $line | cut -d: -f5`
echo scp -p /builds/${BUILDDATE}/Integration/$src ... (1 Reply)
Hi,
I have issued the below command to remove directories under a specific path, it removes them fine. But atlast it tries to
find the same directory and fails.
Directories:
/root/app/dir
/root/app/dir/files/
/root/app/dir/backup/
/root/app/dir/archive/
Command:
find... (1 Reply)
Hi,
I am getting below error in Solaris 10 SPARC when trying to issue a search on /var/tmp partition
Below is the query
/bin/find /var/tmp/ -type f -atime +1
Below is the result
/bin/find: stat() error <File> : No such file or directory (28 Replies)
Hi! I just recently started messing around with Unix, but I've come upon one problem multiple times. Whenever I try to run a shell script, for example;
#! /bin/bash
#--------------------------------------
# example1
#--------------------------------------
echo "Hello, World!"
I... (5 Replies)
Hi Everyone,
I am trying to make this script to use, to find out the DAHDI channel status. Every thing works fine, I even get proper results, however I have this weird error that comes along.
Can someone please help me. Thanks a lot.
#!/bin/bash
# Color to set the test to when a channel is... (3 Replies)
I am new to shell scripting so I assume there is something basic I am missing but I have not been able to figure it out. When I run the following code from a script it can't find the paths to the directory or files. I can literally cut and paste the commands into terminal and they work fine. Why... (2 Replies)
Discussion started by: TryAgain12
2 Replies
LEARN ABOUT NETBSD
npm-run-script
NPM-RUN-SCRIPT(1)NPM-RUN-SCRIPT(1)NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)