How do you run Karma after installation? - javascript

I'm trying to use karma for different watch processes.
I installed karma globally with:
npm i -g karma
Then ran karma start karma.conf.js and it worked.
Now I need to install karma locally inside the project with
npm install karma
It seems to install it fine since I have the folder karma in node_modules, however, node_modules/karma/bin/karma seems not to be the executable file to run.
How should I run karma after installing it locally?

To run locally on Windows (I'm on Windows 10), I recommend adding the following to your package.json file.
"scripts": {
"test": "cd ./node_modules/karma/bin/ && karma start"
},
Then from the command line, type npm run test
I prefer to not install a cli globally for these kinds of tools and instead run them locally from my project using a script. This way I can quickly see what version is in the dev dependencies and don't have to worry about the global version being different from the local one.
"devDependencies": {
"karma": "^1.4.0"
}

To run Karma after installing it locally:
# Run Karma:
$ ./node_modules/karma/bin/karma start
Typing ./node_modules/karma/bin/karma start sucks and so you might find it useful to install karma-cli globally. You will need to do this if you want to run Karma on Windows from the command line.
$ npm install -g karma-cli
Then, you can run Karma simply by karma from anywhere and it will always run the local version.

Related

How to pass scope name to lerna command dynamic?

I use lerna to manage projects and dev command exists in some projects.
For exmaple, A and B have command dev to start project.
I must write two command in root project:
{
"dev:A":"lerna exec --scope A -- yarn dev",
"dev:B":"lerna exec --scope B -- yarn dev"
}
It's there anyway to run like this:
yarn dev A
I try but it's failure. The scope name is pass to yarn dev not lerna.
{
"dev":"lerna exec --scope $1 -- yarn dev",
}
Forget it.
I see the answer and the command "lerna exec 'yarn dev' --scope" works.
The executable is not yarn, but lerna. You want the command to be
lerna run dev --scope xyz
So either install it globally and call it like that, or install it as a project dependency and then
yarn lerna -- run dev --scope ...
# or
`npm run lerna -- run dev --scope ...`
or use npx lerna run dev --scope ... to run it globally without explicit install.
Why that way?
Because yarn <bin>/npm run <bin> executes the bin as if you'd call it directly, and the -- seperates arguments to yarn/npm from arguments to the bin you called. More recent yarns will allow you to drop the -- and figure them out automagically.
I'm not sure if you really need to use yarn dev instead of simply dev in the lerna part of the script, as lerna does just that -- walk all projects, look up if any project has a dev script and executes it (if you use --scope, it will of course only look up the given project(s)...). You might need it with yarn less it calls the commands in the sub-packages using npm instead, but I didn't check that, as our company uses npm.
A package.json including
{
"scripts": { "dev": "lerna run dev --scope x" }
}
does the same thing if you launch it with yarn dev.
If you want to call the lerna-dev script with more arguments, you can always go for yarn dev -- --include-dependencies in the terminal, which will append all arguments after dev to lerna instead of yarn, in this example resulting in yarn lerna -- dev --scope x --include-dependencies

NPM: How to add a "post-install" hook that's not run for package consumers?

I'm writing an NPM module.
I'd like to automate some tasks after every npm install when developing the module locally.
However, I do not want these steps to be performed when consumers of my library perform an npm install and I do not want these steps to be performed after every npm pack and npm publish that I make during development (so this rules-out using the prepublish and prepare scripts).
What's the easiest way to achieve this?
(I've considered: (a) publish a separate package.json w/o the install script, (b) create a ./install.sh in the project's root that users call instead of npm install... but this kinda sucks.)
The install:local script here will run after npm install is run locally only (i.e. not when consumers install your package).
package.json:
{
...,
"scripts": {
"prepare": "case \"$npm_config_argv\" in *\"\\\"install\\\"\"*|*\"\\\"ci\\\"\"*) npm run install:local ;; esac",
"install:local": "echo 'npm install' was run directly in the project, and not by a library consumer!",
}
}

npm script strange behavior using npm terminal

I have this in my package.json
"devDependencies": {
"chromedriver": "^2.37.0",
"geckodriver": "^1.11.0",
"nightwatch": "^0.9.20",
"selenium-server": "^3.11.0"
},
"scripts": {
"e2e": "nightwatch -c tests/nightwatch.conf.js -e chrome"
}
and I'm able to execute npm run e2e
But in my terminal when I do node nightwatch -c tests/nightwatch.conf.js -e chrome I got this error
Error: Cannot find module 'C:\Users\James\Documents\sample_project\nightwatch'
Just curious, what's the problem? I doubt I know how npm and node work now.
When you do 'node nightwatch' it should go into node_modules folder and look for nightwatch, but instead its looking in the root directory.
You could cut the nightwatch folder in node_modules and move it to the same directory as package.json. Give it a try!
Is nightwatch module installed globally? If not, then install this module globally first using npm install nightwatch -g. As you are using this module inside CLI command, hence this must be installed globally in the system.
Sometime there might be issue with npm cache. Try to clean up the npm cache using:
npm cache verify
npm cache clean --force
npm cache clear --force
Then you can run npm install and npm install nightwatch -g again, just to make sure all modules are installed.
Moreover, you can try to use --verbose in your command like:
node nightwatch.js --verbose
And see the output, may be this help to debug the issue.

nodemon command is not recognized in terminal for node js server

I am doing node.js server setup from https://scotch.io/tutorials/authenticate-a-node-js-api-with-json-web-tokens. I am new in node.js. I am installing npm install nodemon --save. But when I am run the server with this nodemon server.js.
In the terminal showing:
nodemon is not recognized as internal or external command, operable
program or batch file
node server.js command is working and started the server, But nodemon command is not working.
I am set up the node js server from https://scotch.io/tutorials/authenticate-a-node-js-api-with-json-web-tokens video.
I don't know why it is not working I have tried some command for the install nodemon.
npm install -g nodemon
npm install -g nodemon --save
npm install --save-dev nodemon
npm install -g nodemon#debug
npm install -g --force nodemon
I have seen one link I can´t install nodemon globally, "nodemon" not recognized, But I don't know how to set the path because of my project location in D drive.
I want to run nodemon server.js. How can this be done?
You need to install it globally
npm install -g nodemon
# or if using yarn
yarn global add nodemon
And then it will be available on the path (I see now that you have tried this and it didn't work, your path may be messed up)
If you want to use the locally installed version, rather than installing globally then you can create a script in your package.json
"scripts": {
"serve": "nodemon server.js"
},
and then use
npm run serve
optionally if using yarn
# without adding serve in package.json
yarn run nodemon server.js
# with serve script in package.json
yarn run serve
npm will then look in your local node_modules folder before looking for the command in your global modules
Install nodemon globally:
C:\>npm install -g nodemon
Get prefix:
C:\>npm config get prefix
You will get output like following in your console:
C:\Users\Family\.node_modules_global
Copy it.
Set Path.
Go to Advance System Settings → Environment Variable → Click New (Under User Variables) → Pop up form will be displayed → Pass the following values:
variable name = path,
variable value = Copy output from your console
Now Run Nodemon:
C:\>nodemon .
No need to install nodemon globally. Just run this npx nodemon <scriptname.js>. That's it.
First, write npm install --save nodemon
then in package.json write the followings
"scripts": {
"server": "nodemon server.js"
},
then write
npm run server
I was facing the same issue. I had installed nodemon as a dev-dependency and when I tried to start the server it gave the message that
nodemon is not recognized as internal or external command, operable
program or batch file
Then I installed it globally and tried to start the server and it worked!
npm install -g nodemon
To use nodemon you must install it globally.
For Windows
npm i -g nodemon
For Mac
sudo npm i -g nodemon
If you don't want to install it globally you can install it locally in your project folder by running command npm i nodemon . It will give error something like this if run locally:
nodemon : The term 'nodemon' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is
correct and try again.
To remove this error open package.json file and add
"scripts": {
"server": "nodemon server.js"
},
and after that just run command
npm run server
and your nodemon will start working properly.
This may come to late, But better to say somthing :)
If you don't want to install nodemon globbaly you can use npx, it installs the package at run-time and will behave as global package (keep in mind that it's just available at the moment and does not exist globally!).
So all you need is npx nodemon server.js.
npx can be used out of the box from npm#5.2.0 version and up.
I had the same error a few minutes ago and this is how I've solved it:
1. Install "nodemon" Globally
npm install nodemon -g
2. Then you need to add the npm path to the environment variables
To find the path do this in the terminal:
npm config get prefix
You'll get the output that looks like this: C:\Users\user\AppData\Roaming\npm
If you're not sure about how you can update environment variables on Windows, check this out: Here
3. Run the app again with "nodemon"
Before you run the app, create a new terminal to make sure that the terminal recognises the changes in the environment variables.
Then run:
ex:
nodemon server.js
Does it need to be installed globally? Do you need to be able to just run nodemon server.js ? If not, you could always just call it from your local project directory. Should be here:
node_modules/.bin/nodemon
This line solved my problem in CMD:
npm install --save-dev nodemon
I tried installing the nodemon globally but that doesn't worked for me.
whenever i try to run it always shows me the error:
nodemon : The term 'nodemon' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is
correct and try again.
2. I have found two solutions for this
solution 1:
What i have tried is to update the "scripts" in package.json file and there i have added
"server": "nodemon app.js"
above line of code and after that
npm run server
Soluton 2:
Press the Windows key.
Type "Path" in the search box and select "Edit the system environment variables"
Click on "Environment Variables" near the bottom.
In the "System Variables" section double click on the "Path" variable.
Click "New" on the right-hand side.
Copy and paste this into the box (replace [Username]):
C:\Users[Username]\AppData\Roaming\npm
restart your terminal and VSCode.
Then type nodemon app.js to run the nodemon
i applied solution 2 as we just need to run nodemon [filename.js]
I have fixed in this way
uninstall existing local nodemon
npm uninstall nodemon
install it again globally.
npm i -g nodemon
It is better to install nodemon globally instead as dev dependency to the project.
npm install -g nodemon
Official NPM CDN: Link
This package is used to monitor changes in the javascript files and re run the npm start so that it is easy to dev purposes.
Since node prefix is not in the PATH ENV variable , any of the globally installed modules are not getting recognized.
Please try this.
Open cmd prompt
npm config get prefix
append the resulting path to PATH env variable.
Now you should be able to run nodemon from any location.
try this link and follow it.fixing npm permissions
https://docs.npmjs.com/getting-started/fixing-npm-permissions#option-2-change-npms-default-directory-to-another-directory
You can run your node app by simply typing nodemon
It First run index.js
You can put your entry point in that file easily.
If you have not installed nodemon then you first you have to install it by
npm install -g nodemon
If you got any permission error then use
sudo npm install -g nodemon
You can check nodemon exists or not by
nodemon -v
For me setting the path variables was enough for the solution:
Step 1) Install nodemon globally using npm install -g nodemon
Step 2) Set the ENVIRONMENT VARIABLES, by adding npm path the PATH variable
1) Open Control Panel, search for environment variable
2) Click open the environment variable
3) Create new variable NPM set it with the path of npm as appears from the nodemon installation cmd output (as seen from nodemon installation screenshot):
4) Now add NPM variable to the PATH variables:
Step 3) Close the 'cmd' and open a fresh one and type nodemon --version
Now we have the nodemon ready to use :)
This issue is also possible if running scripts is disabled on the system. In order to enable it:
Open Windows PowerShell with Run as Administrator
Execute:
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
npm install -g nodemon
nodemon app
Just had the same problem after creating a new user profile on my development machine.
The problem was that I wasn't running the console (command prompt\powershell ISE) as admin.
Running as admin solved this problem for me.
Just install Globally
npm install -g nodemon
It worked for me on Windows 10.
nodemon app.js
The Set-ExecutionPolicy cmdlet's default execution policy is Restricted for Windows.
You can try installing nodemon by setting this policy to Unrestricted.
execute command : Set-ExecutionPolicy Unrestricted
and then try installing nodemon and execute command: nodemon -v
First you need to install nodemon globally by using this command:
"npm i -g nodemon" (for Windows) and "sudo npm i -g nodemon" (for Mac)
then run
"nodemon app.js"
Now you will be fine.
Run this command:
npm install nodemon -g
Now it will install the nodemon but the problem with my case is that it is installing nodemon somewhere else.I added Nodejs path from (ProgramFiles(x86)) but that did not worked so i found another solution.
Run above command
There will be a path shown during installation where nodemon is installed,then
[Kindly go to below link to see the path][1]
[1]: https://i.stack.imgur.com/ld2sU.png
Copy the path upto npm and set it to environment variable
Now try the below command,hopefully it will run
nodemon YourAppName.js
All above options are failed, I got the permanent solution for this.
Add below line in package.json under dependencies and run npm install. This will add nodemon package to node_modules and there you go, enjoy the coding.
"nodemon": "^1.17.*"
Try in your packge.json:
put "./node_modules/.bin/nodemon" instead of just "nodemon".
For me it works.
This help me with the same problem to start both nodemon and graphql servers
npm run dev
Step 1: $ npm install nodemon --> install nodemon on your project
Step 2: Add serve in script on package.json file as:
"scripts": {
"serve": "nodemon app.js" // you can change file name accordingly
}
Step 3: $ npm run serve
The following worked for me on windows 11.
Type npm install in the terminal. (Within the same directory as the project)
Then type npm run serve to run the application from the default browser.
Remove nodemon because it's a dev dependency and use node instead of it.
"scripts": {
"start": "node server.js"
},
This worked for me.

Grunt not being added to Environment Variables Path

I installed the Grunt cli with the following command?
npm install -g grunt-cli
Then I created the package.json and the Grunfile.js and run
npm install -S grunt
But grunt is not known by Windows. It says "´grunt´ is not recognized as an internal or external command".
Typing path on console, doesn't show Grunt, and where grunt also fails.
Did everything as Administrator on a Windows 8 machine.
What is wrong with this installation?
obs: and where is it installed?

Categories