This answer worked for me: https://stackoverflow.com/a/55541435/3051080 TL;DR; update git cache: git rm -r –cached . git add –all . git commit -a -m “Versioning untracked files” git push origin master
Try quotes: npm install “@angular2-material”
In some networked environments (such as a container running nodemon reading across a mounted drive), you will need to use the legacyWatch: true which enabled Chokidar’s polling. Via the CLI, use either –legacy-watch or -L for short: nodemon -L
I got this error because of an older version of rxjs and Angular 6 needs the latest version of rxjs. This command installs the latest version that is compatible with Angular 6. npm install –save rxjs-compat
import defaultExport from ‘./local-file’ Or import { namedExport } from ‘./local-file’
I think the root of your problem is likely caching. NPM caches packages that have been downloaded, so they don’t have to be downloaded again, and they can even be re-installed offline if necessary. It also caches the resolved value for later use. If a package of the same version has already been resolved and … Read more
I agree with @RobC here. It also disactivated running custom scripts in my package.json completely for me, which obviously is a deal breaker since you can’t define and run your custom scripts anymore. Although it’s probably useful to think about these security concerns, I don’t think running npm config set ignore-scripts true is the right … Read more
I don’t have a good environment to test this in right now, but my guess is that it would look something like: gulp.task(“js”, function(){ var destDir = “./dist”; return browserify([ “./js/app.js”, “./js/public.js” ]) .bundle() .pipe(source(“appBundle.js”)) .pipe(gulp.dest(destDir)) .pipe(rename(“publicBundle.js”)) .pipe(gulp.dest(destDir)); }); EDIT: I just realized I mis-read the question, there should be two separate bundles coming from … Read more
I noticed a similar warning today . The issue went off after I deleted package.json file.I had used yarn and npm interchangeable until now in my side project. ‘npm install’ creates package-lock.json and ‘yarn install’ generates yarn.lock . Normally you stick to either one of the package managers in your project