thisismynota

Saturday, April 2, 2022

NPM - 'cross-env' is not recognized as an internal or external command

 How to solve this problem? super easy:

  1. Remove node_modules folder
  2. Remove package-lock.json
  3. Run npm install

By YourAdmin @ 3:16 AM No comments:
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

Favorite Links

  • Control All Of Your Wordpress Sites From One Central Location.

Blog Archive

  • ▼  2022 (5)
    • ►  September (2)
    • ►  May (2)
    • ▼  April (1)
      • NPM - 'cross-env' is not recognized as an internal...
  • ►  2017 (2)
    • ►  November (1)
    • ►  January (1)
  • ►  2016 (5)
    • ►  December (1)
    • ►  August (1)
    • ►  June (3)
  • ►  2015 (10)
    • ►  November (1)
    • ►  September (3)
    • ►  June (1)
    • ►  May (3)
    • ►  February (1)
    • ►  January (1)
  • ►  2014 (1)
    • ►  February (1)
  • ►  2013 (11)
    • ►  December (1)
    • ►  November (2)
    • ►  October (3)
    • ►  September (2)
    • ►  April (3)

Labels

  • 11g (1)
  • apache (1)
  • backup (1)
  • BCM43142 (1)
  • broadcom (1)
  • ca (1)
  • CAS (1)
  • centos (13)
  • certificate (1)
  • codeigniter (1)
  • composer (1)
  • cron (2)
  • dd (1)
  • entrust (1)
  • error 1140 (1)
  • error 1290 (1)
  • event (1)
  • explode (1)
  • index.php (1)
  • jasig cas (1)
  • java (1)
  • laravel (1)
  • laravel 4 (1)
  • LDAP (1)
  • linux (15)
  • maven (2)
  • mysql (6)
  • nginx (1)
  • oracle (2)
  • php (4)
  • programming (2)
  • redhat (1)
  • sdhc (1)
  • ssl (1)
  • SSO (1)
  • svn (1)
  • tomcat (1)
  • trim (1)
  • ubuntu (1)
  • vm (1)
  • vmware (1)
  • weblogic (1)
  • wireless (1)
  • xampp (1)
Powered by Blogger.