Npm DalekJS: tests are not running, at all

Here's my set up on Ubuntu dalek and dalek-cli installed as instructed in the website, the version is displayed correctly phantomjs was installed via npm install but the phantomjs command could not be run installed phantomjs via apt-get ... now I have version 1.4 in the folder /var/www/first_tests/ I have the package.json file provided in the website along with a subfolder tests containing first.js with the google example provided I am in my homedirectory since that's the only place I can ca

sudo npm install -g mocha not working

I am just running a basic mocha install command and its throwing the error in the mac terminal, Please suggest seeing the logs what can i do to get this running, Really appreciate the help. AUK03154:~ itrmg$ sudo npm install –g mocha Password: npm ERR! 404 404 Not Found: %E2%80%93g npm ERR! 404 npm ERR! 404 '%E2%80%93g' is not in the npm registry. npm ERR! 404 You should bug the author to publish it npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder,

Publish npm package on guest computer

I had published an npm package on my personal pc. Say, i am away from my personal PC and i wish to update the npm package from a guest computer. Do i need to adduser to guest computer from command line? Is there any browser based way to update the package?

PhpStorm Npm and Gulp tool windows missing in some projects

For all projects I have gulpfile.js in the project's root (also bower.json, package.json and node_modules). In PhpStorm Settings > Languages & Frameworks > Node.js and NPM I can see all the (local and global) packages. However, in some projects PhpStorm shows the npm and Gulp tool windows... and in other projects it doesn't. Anybody else ran into this problem? The only (consistent) difference between the projects that have those tool windows and the ones that don't is: the projects for whi

WebStorm - error: Please specify npm package

Webstorm throws an error when trying to run a command specified in package.json: "devDependencies": {}, "scripts": { "dev": "./node_modules/.bin/webpack-dev-server --content-base src --inline --hot", "test": "echo \"Error: no test specified\" && exit 1" }, I've used this script with Webstorm on other computers (Linux/Windows). On this one (Linux), it does not seem to work out of a sudden. It used to be fine. I've just upgraded Webstorm. From CLI, the 'dev'c

Npm Webpack / ES6: how to import stylesheets

I see repositories like bootstrap starting to include additional tags in their package.json file such as 'style' and 'less.' How can I use these tags to import assets? package.json { "name": "bootstrap", "style": "dist/css/bootstrap.css", "sass": "scss/bootstrap.scss", "main": "./dist/js/npm" } I am using ES6 modules and webpack. I want to do be able to import my stylesheets using the style tag in package.json. Currently I am doing something like this: my_stylesheets.less @import

Npm Run phantomjs and casperjs on local folder

I'm looking for a solution about one problem. I want to install and use the library casperjs without install anything globally on the machine. First i try to install just by npm install casperjs (https://www.npmjs.com/package/casperjs) Obviously, this is the error message : casperjs : commande introuvable I try to use static path : ../../node_modules/casperjs/bin/casperjs scriptCasperJS.js New error : Fatal: [Errno 2] No such file or directory; did you install phantomjs? So i download and

Npm Yeoman project aborting due to not finding compass

Following a tutorial from "JavaScript Frameworks for Modern Web Development" (ch. 3 on Yeoman) to setup Yeoman and scaffold a simple project: Working in git-bash, I installed the Yeoman generator "modernweb" (cmd: npm install -g generator-modernweb) and successfully scaffolded my project (cmd: yo modernweb). When I run the grunt command to build and launch, I get the following error: Warning: not found: compass Use --force to continue Aborted due to warnings I can find the compass module in

fish shell and global npm modules

I'm experiencing some issues with my local environment. I'm using: homebrew (1.1.4) fish shell (2.4) n version manager (2.1.0) node npm All of the above were initially installed via homebrew. Issues: Any globally installed modules cannot be run. I cannot update npm versions. The node versions I use regularly are 0.10.48 and 6.9.2 - but mostly 4.6.2. I've created some aliases in fish to be able to get the the global modules to run. I'd prefer to address the root cause rather than conti

What does -s mean in npm command?

I saw the following command that includes -s option. What does it(-s) mean? Because I didn't see the option in package.json. $ npm run dev -s

Prevent Facebook Flow from checking linked npm package

I have a React Native application with a linked dependency which lies in the same parent folder: home / app / node_modules / [common_stuff] common_stuff / ... In my .flowconfig I have these lines: [ignore] ../.* <PROJECT_ROOT>/node_modules/common_stuff/.* When I run flow it gives me this error: ../common_stuff/node_modules/find-elm-dependencies/test/fixtures/malformed-elm-package-json/elm-package.json: 1: {-{ malformed JSON }-} ^ Unexpected token - How can I prevent it

npm5 equivalent to yarn's --pure-lockfile flag?

I'm looking for an equivalent for yarn's --pure-lockfile flag. This flag is useful when installing dependencies in CI, when you want it to read your lockfile but not modify it. Does npm v5 have an equivalent?

what is gulp.js and how it is related to npm

I am new to the development based on java-script frameworks. I want to understand gulp, npm. Somewhere, I read that these are open source client side development tool but I could not get more insight on this. Please help!

npm ENOSELF error - installing a package in its gh-pages branch

I'd like to write some documentation for a JS Lib on GitHub, using the Lib itself. I created an empty branch called gh-pages and started building the documentation pages. Now I need to write some Javascript using the Lib I'm documenting, because who wouldn't use their own Library. I tried installing it via npm install but obviously got this error: npm ERR! code ENOSELF npm ERR! Refusing to install package with name "package" under a package npm ERR! also called "package". Did you name your proj

.npmignore: ignore whole folder except given file types

I have a typescript project that I am publishing to npm. All my TS sources are in a folder called src and these are compiled to a folder called dist. src is likely to include some html templates, possibly css files and other assets. As part of the build these assets are all copied to the dist folder. Source map files are also generated in the dist folder When publishing I only really want to publish the dist folder but I want the source maps in the dist folder to work. What I am trying to ach

Using npm or Bower in Visual Studio for Mac

I have a situation in which I need my ASP.NET Core 2 MVC project to be cross-platform. Unfortunately it appears that I can't use Bower or npm integrated into the IDE (as I can with Visual Studio 2017), so I'm going to need a solution that works for both platforms in order to include the packages I need (https://fullcalendar.io/ being a specific example). Package managers are mostly foreign to me, so this may be trivially easy but I just need to know how I can approach this in a way that works

nexus npm publish failed with error -4048

I'm trying to publish my private module to a new setup nexus OSS 3.8.0-02 (running in sonatype/nexus3 docker container), and hit an error with errno: -4048. My npm version is in: node v8.9.4 and npm v5.6.0 I have already try to add my base64 encoded username and password in .npmrc which under my C:\Users\AHOU\ directory like so always-auth=true _auth="<generated base64>" email=anselmhou.ps@gmail.com prefix=C:\kits\npm @ngpf:registry=http://<nexus server ip>:28081/nexus/repository

Integrate NPM build in ANT script

I have an existing ANT file to build java code. I need to integrate the following command in the build: 1) npm install 2) npm run build How can I integrate it? I believe I need to add a new target to run these command but not sure about exact code/xml changes.

Why doesn't npm install build the dependency?

I forked a npm module git to my repo and listed it as a dependency in my project. "dependencies": { ... "mobx": "git+https://github.com/myaccount/mobx" } this module will be downloaded in node_modules directory when I run npm install but it doesn't build. So I have to go to this directory and run npm install manually. Is there any way for me to configure it to build the dependnecy with npm install on the root of my project. The scripts in package.json for the forked repo looks like:

How to fix npm package braces issue with react-scripts v2.1.5 when npm audit does nothing?

My NPM package in my react client folder is giving me 63 low vulnerabilities all dealing with the braces package mainly in the jest folder of the react-scripts package of version 2.1.5. NPM Audit fix doesn't work, what do I do? I've tried downgrading to previous versions of react-scripts, updating braces either through updating the package.json, deleting the package lock, and running npm install again, or running npm update braces, but nothing has worked after 2 hours of fiddling. I've also tri

Is there a workflow for developing private, interrelated npm packages as a team?

We are trying to use private npm packages across our app for all their benefits (reusing common components, insulating change, control over versions, etc); but as the app goes from a single dependency to nested dependencies, we can't find an efficient way to move from npm linked packages to published and deployed packages within our gitflow workflow. For example, given this package structure: -@mine/master-app |-@mine/base |-@mine/mock-data |-@mine/subApp |-@mine/base |-@mine/sub

Npm Unable to locate package, which has been installed

I am using homestead environment with Vagrant version 2.2.4, homestead 7.2.1 and npm 6.7.0. I am attempting to install and use a module called 'vuetify-material-dashboard'. I've installed the module with npm npm install --save vuetify-material-dashboard I've loaded the module in my app.js import Vue from 'vue'; import VueRouter from 'vue-router'; import routes from './routes'; import VueResource from 'vue-resource'; import { TableComponent, TableColumn } from 'vue-table-component'; impor

Npm Difference between package.json dependencies and published dependencies?

When looking at a package published on npm, e.g. https://www.npmjs.com/package/react-router, and looking at the package.json for the same version in the source, there is a vast difference in dependencies. For the example react-router, the webpage lists 10 dependencies and the package.json 27. My assumption is that package.json is the source of truth, so why is there a difference?

I deleted npm but its still there

I want to delete npm from my system and start with a clean slate. So I run sudo apt remove npm. Now, I called npm -v and it returned 6.13.7. What dose that mean? is it possible that I have two or more installations of npm on my system? which one is considered "global"? If I run whereis npm I get /usr/local/bin/npm and ls over there tells me its a soft link that points to /usr/local/lib/node_modules/npm Should I simply rm * the folder and the link?

Npm Installing webpack ^4.42.1 gives me deprecated warnings

I get the following two warnings on a npm install: npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated Not sure if we should just ignore this warning or fix it? If so, how.

`npm install @babel/cli` says "WARN deprecated" for four modules. How can I fix these deprecations?

My setup MacOS = Catalina 10.15.4 (latest version) nvm = 0.35.3 (latest version) node.js = 12.16.3 (latest LTS version). Installed inside of nvm directories. npm = 6.14.4 (latest version). Installed inside of nvm directories. note: no global installations inside of usr/local. My problem I use npm init -y to create my package.json. No problems here. I use npm install --save-dev @babel/core. No problems here. I get version 7.9.6. Then when I use npm install --save-dev @babel/cli I am getti

Npm Warning while installing adonis cli

I was installing adonis cli in my local project. The following error showed up. npm i @adonisjs/cli npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. Currently i am running on node js v 12 on my local machine and server. Will it be a problem once node LTS version goes up to 14+ or it will be a

Is there a way for `npm pack` to include all dependency packages recursively instead of just the base package? Why does it do that?

For example in this picture: npm pack only packages the contents of electron-builder@22.8.1, but I'd like it to package all of the required 14 dependencies and then its children dependencies recursively until I know I could use electron-builder@22.8.1 correctly with a npm install with no troubles. Is there a way to do this? Why does npm pack only do the top level instead of all the packages associated with it? For context, I'm going this way instead of simply npm install electron-builder becaus

Npm Microsoft Teams Application Authorization: ngrok gateway error The server returned an invalid or incomplete HTTP response

Summary: I am currently building a Microsoft Teams application with Outlook API support for sending messages within teams. In order to make these calls I am setting up Authentication using the Microsoft graphs methodology. I am currently following this tutorial: https://github.com/aycabas/TeamsApp I am able to get through all of the steps with setting up authentication but when attempting to load the application in teams I am met with this error: ngrok gateway error The server returned an invali

Npm adding a package using yarn downgrades version of some other existing package

I've installed a yarn package called @drizzle/store which has a dependency of web3@1.3.0 which also got installed successfully. Now I tried installing a yarn package called @toruslabs/torus-embed which has a dependency on web3@0.20.7, and it downgraded the existing web3@1.3.0 to web3@0.20.7. This is causing problems in my app which requires the latest web3@1.3.0 version. Any way this can be rectified without monkey-patching with latest web3 version every time torus_embed package is installed? Ev

Set NPM log level to "quiet" in script definition

I have a simple CLI tool for my project which I run through NPM/Yarn scripts: "scripts": { "cli": "dotenv ts-node -r tsconfig-paths/register src/cli/index.ts --", ... } I'd like to silence the log info stuff that NPM/Yarn automatically write to stdout when a script is run. By default, the output is: $~/foo> yarn cli --help yarn run v1.22.5 $ dotenv ts-node -r tsconfig-paths/register src/cli/index.ts -- --help cli <command> Foo bar baz bat Optio

Npm Is it possible to specify a runtime dependency of a code generator?

I am working on an npm package that is used as a CLI to generate code. It makes sense that this project should generally be used as a devDependency. But the generated code will require a third-party library at runtime. Is there a way to manage this dependency via package.json? I have seen other libraries include a note in the README that defines this dependency, but there is no guarantee that the end user will read this README, so I would like to be able to enforce this. One thought I had was to

Run npm script command in current shell

I'm using npm run-script feature, and would like to run commands that should effect the current shell. For example I would like to be able to export variables or source a file. "scripts": { "example": "export name=eden && source someVirtualenv/bin/activate", } It seems that npm automatically creates a sub process, is there a way to make it run on current shell?

npm run <script-name> is not working

I've defined scripts in my package.json like this: "scripts": { "build": "webpack", "start": "webpack-dev-server --inline --hot --host 0.0.0.0" }, I have problems running them. When i try npm run startor npm run build I always get: Lifecycle scripts included in iski.world: start webpack-dev-server --inline --hot --host 0.0.0.0 available via `npm run-script`: build webpack However running npm start works. Node version: 5.1.0 npm version: 3.3.12

Npm Different package versions for Android and iOS

I am developing an app for both Android and iOS using React Native. One of the libraries I'm using is a bit problematic because the app only compiles correctly: ...on Android when using "react-native": "0.42.0". ...on iOS when using "react-native": "0.37.0". (Neither the library itself , nor the specific versions of react-native are important for this discussion. What's important is that I seemingly need two separate versions "at the same time" - a different one for each platform.) I'm lo

Npm systemctl command in centos

I am trying to execute npm run command as background process in centos by creating it as systemd service . But when I am trying to start, it is giving error Unit not found and when running systemctl enable it gives error as no such file or directory.

Npm Import CSS from node_modules using Gulp-SASS

I want to import a CSS-file from my node_modules using SASS. @import 'normalize.css/normalize'; This is how my gulpfile.js handles my SASS: const gulp = require('gulp'), sass = require('gulp-sass'); gulp.task('sass', function () { return gulp.src(['source/assets/css/**.scss', '!source/assets/css/**/_*.[scss|sass']) .pipe(sass()) .pipe(gulp.dest('output/assets/css')); }); SASS compiler will not import the css from node_modules. Instead, this will throw an error. Error: Fil

Npm How to speed up webpack development

Is there any way to also set up webpack to work in a fast developement mode? If only it could be like editing files without a bundler. Make a change - view in browser immediately. A bit of context: As far as I know, the goal of using webpack is to pack what you need into as few files as possible and be able to cleanly require() across .js files, but it has the large downside of taking anywhere form a few seconds to mutliple minutes in order to build it, completely destroying a developers headspa

Azure DevOps buids failing all of sudden and issue looks to be auto-updated NPM version

The build is failing with: "Error: Npm failed with return code: 9009" When we look at, here's what we noticed: Till date (where there were no issues), build used to run on nmp 6.9.0 and node v10.16.3 Since the build started failing, we noticed the versions got auto-upgraded to npm/6.12.0 node/v12.13.0. Please advise how to revert back to older versions, or do if we need to see this issue in a different dimension?

npm install fails with 'error-ex@^1.3.1' is not in the npm registry

npm install fails with the following error: ⠼ Installing packages...npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex npm ERR! 404 npm ERR! 404 'error-ex@^1.3.1' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of 'parse-json' npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

can't install any atom packages with npm error

unable to install any packages on atom. The error is npm ERR! code Z_BUF_ERROR npm ERR! errno -5 npm ERR! zlib: unexpected end of file npm ERR! A complete log of this run can be found in: npm ERR! /Users/yaoli/.atom/.apm/_logs/2020-02-17T09_39_31_164Z-debug.log I have tried to clean the npm cached and reinstall npm. It didn't work.

Npm CleanWebPackPlugin Error :CleanwebpackPlugin is not a constructor

Im trying to use this plugin: CleanWebpackPlugin. But it's not running, i can see the Error: "TypeError: CleanWebPackPlugin is not a constructor" even if i tried all upgrades from the github page: https://github.com/johnagan/clean-webpack-plugin/issues/106 this is my package.json file: { "name": "------", "version": "1.0.0", "description": "", "scripts": { "dev": "webpack-dev-server", "build": "webpack", "test": "echo \"Error: no test specified\" && exit 1" },

nuxt: command not found | Having to use npx instead of npm

I'm trying to create an SSG website with nuxt.js but when I try to run nuxt build && nuxt export or any other nuxt command in the VS Code terminal I get this error: bash: nuxt: command not found. I have these installed: node 12.18.2 npm 6.14.6 nuxt 2.13.3 (globally) I also run VS Code as an administrator on Windows 10 I can run the commands with this format: npx nuxt build && npx nuxt export (adding npx before nuxt), it's a quick fix but I'd like to know what I'm doing wrong. I

How can i upgrade my npm version in windows 10?

I want to upgrade to npm version in between 5-6, since I'm getting the start command error frequently. When I typed the upgrade command for npm like this: npm install -g npm-windows-upgrade In the first phase, I get the following error: npm ERR! cb.apply is not a function Please can anyone help me out!

Npm I can't get id or data-test in cypress recently

I'm trying to get a button with [data-test=ex_button] and click on it in cypress with using the following code: cy.get('[data-test=ex_button]').click({ force: true }) and my UI code: <el-button data-test="ex_button" type="primary" class="button-flat pull-right" @click="myFunction"> {{ tr('myButtonName') }} </el-button> But Cypress fails with the following error message: Timed out retrying: Expected to find element: [data-test=ex_bu

Install subset of dependencies with npm

Is there a way to specify subsets of dependencies in npm, with an alias or "feature tag"? That is, if someone knows that they will only be using some limited subset of the features of my package, they can specify those features and, on npm install, only download the dependencies relevant to those features? My package has a very large number of dependencies and takes nearly half an hour to install, but most users only need a subset of their functionality. I'm thinking of something like how depen

`npm i core-js@latest` won't install because it can't build... core-js@<3.3?

I'm trying to revive the build for an old, unmaintained library so that we can check in some changes (or publish a fork) that lets it play nicely with another updated library (namely Bootstrap 4, but that's not important for this question). When trying a vanilla npm i, well, first I got some places where the library's package.json conflicted with its dependencies' dependencies because of ~ vs ^ conflicts -- the dependencies were more lenient about versions, so I changed a few dependencies in the

  1    2   3   4   5   6  ... 下一页 最后一页 共 17 页