package.json

I have an Angular 5 App. This is what I have in my package.json { "name": "web", "version": "0.0.0", "license": "MIT", "scripts": { "ng": "ng", "start": "node server.js", "build": "ng build", "test": "ng test", "lint": "ng lint", "e2e": "ng e2e", "postinstall": "ng build --aot --prod" }, "private": true, "dependencies": { "@angular/animations": "5.1.0", "@angular/cli": "^1.6.4", "@angular/common": "5.0.3", "@angular/compiler": "5.0.3", "@angular/compiler-cli": "5.0.3", "@angular/core": "5.0.3", "@angular/forms": "5.0.3", "@angular/http": "5.0.3", "@angular/platform-browser": "5.0.3", "@angular

My question concerns an existing library that I wish to publish as an NPM module. The library is already in use, and currently require d via the local file system. How can I specify the root directory of my module's files? If I have a structure like: . ├── package.json ├── src | ├── js | └────── lib | └───────── my | └───────────── thing.js | └───────────── that.js How do I specify that the root of my module, and accessible files is src/js/lib/my/ ? I would like to use as follows from an outside project: var thing = require('my/thing'), that = require('my/that'); I saw the "files" property in

Q: Is it possible to change the the context in which npm runs scripts? What I want to is the following: "scripts": { "test": "gulp mocha", "pre-install": "./deps/2.7/cpython/configure --prefix=$(pwd)/build --exec-prefix=$(pwd)/build && make -C deps/2.7/cpython && make -C deps/2.7/cpython install", "install": "node-gyp rebuild" }, Obviously cd deps/2.7/cpython/ && ./configure would work on UNIX-like systems but not on windows. Why: The root of the problem is, that the configure command of the python repo outputs files into the directory where it is called. The files however are build relevant

I would like to start working with the Angular2 Beta, but I am facing a few problems regarding the required libraries. I am using Eclipse and it's TypeScript Plugin . Also, I am using SystemJS as module loader. My problem is that if I install Angular2 using npm install angular2 it loads the whole Angular-Project, including the CommonJS -Version, ES6 -Version and the TypeScript -Version. This results in a over 30 MB big folder with almost 2000 files, though I only need the TypeScript -Version (still a few 100 files), without examples. Also, importing the /ts -folder in Eclipse gives me errors,

So I am using eslint as a linter for my react project and I would like it to check all of my .js files. I am able to do this through the script: "lint": "eslint back/*.js && eslint backTest/*.js && eslint front/actions/*.js" how can I get it to examine every .js file recursively, something like: "lint": "eslint -r *.js" This would save me having to type out each file inidvidually Thanks in advance for the help eslint "**/*.js" to run on all js files in all the folders recursively (in the current folder) You can also do: AnyFolder/**/*.js And to ignore a folder: eslint "**/*.js" --ignore

I want to reference my package version in a npm script so I can show current version in the app. Something like { "name": "bla", "version": "1.0.0", "author": "bla bla", "scripts": { "build": "node VERSION=<<package.version>> build/build.js" } } Is there a way to do this? 1) Referencing package version in npm-scripts. In npm-script 's you can reference the version using the variable npm_package_version . For example: Using a bash shell (E.g. Linux, macOS): { ... "version": "1.0.0", "scripts": { "build": "echo $npm_package_version" } } Note the $ prefix Using Windows (E.g. cmd.exe, Powershell):