Package is deleted at NMP install - node.js

Problem:
Package Now-UI-kit folder is deleted as soon as I run 'npm install' or if I install a package via 'npm install [package name]'
I have a development environment with a build tool for the development of my site. The environment has the Bootstrap framework and a lay-out kit: Now-UI-Kit. This is a template I bought. Based on the documentation of Now-UI-kit I have to run 'npm install' from the folder where the kit is installed. One folder up is node_modules. Below a tree, seen from the node_modules folder:
➜ node_modules git:(master) ✗ tree -L 2
.
├── bootstrap
│   ├── LICENSE
│   ├── README.md
│   ├── dist
│   ├── js
│   ├── package.json
│   └── scss
├── cookies-eu-banner
│   ├── Gulpfile.js
│   ├── LICENSE
│   ├── README.md
│   ├── bower.json
│   ├── css
│   ├── demo
│   ├── dist
│   ├── package-lock.json
│   ├── package.json
│   └── src
├── dyscrollupjs
│   ├── Gruntfile.js
│   ├── LICENSE
│   ├── README.md
│   ├── dist
│   ├── index.html
│   ├── package.json
│   ├── src
│   └── tsconfig.json
├── jquery
│   ├── AUTHORS.txt
│   ├── LICENSE.txt
│   ├── README.md
│   ├── bower.json
│   ├── dist
│   ├── external
│   ├── package.json
│   └── src
├── jquery_lazyscript
│   ├── jquery.lazyscript.js
│   ├── jquery.lazyscript.js.map
│   ├── jquery.lazyscript.min\ kopie.js
│   ├── jquery.lazyscript.min.js
│   └── jquery.lazyscript.min.js.map
├── now-ui-kit-pro
│   ├── CHANGELOG.md
│   ├── README.md
│   ├── assets
│   ├── docs
│   ├── examples
│   ├── gulpfile.js
│   ├── index.html
│   ├── node_modules
│   ├── nucleo-icons.html
│   ├── package-lock.json
│   ├── package.json
│   ├── presentation.html
│   └── sections.html
├── popper.js
│   ├── README.md
│   ├── dist
│   ├── index.d.ts
│   ├── index.js.flow
│   └── package.json
├── rellax
│   ├── LICENSE
│   ├── README.md
│   ├── bower.json
│   ├── css
│   ├── demo.html
│   ├── package.json
│   ├── rellax.js
│   ├── rellax.min.js
│   └── tests
├── resize_header
│   └── resize_header_logo.js
├── scripts
│   ├── jquery.lazyscript.min.js
│   ├── lazyload.js
│   └── rellax_parameters.js
└── social
├── changed\ -\ social.js
├── defer.js
└── social.js
The latest version of the Now-UI-kit I downloaded from the builder is v 1.2.2 and the latest version on npm is v1.1.0 enter link description here
A snippet from the package json in the src-folder (one folder higher than node_modules)
"dependencies": {
"bootstrap": "^4.2.1",
"cookies-eu-banner": "^1.2.14",
"dyscrollupjs": "^2.0.0",
"jquery": "^3.3.1",
"now-ui-kit-pro": "^1.2.2",
"popper.js": "^1.14.6",
"rellax": "^1.7.2"
},
The package json from the Now-UI-kit contains:
{
"name": "now-ui-kit-pro",
"description": "Premium Bootstrap 4 Now UI Design",
"version": "1.2.2",
"homepage": "http://creative-tim.com/product/now-ui-kit-pro",
"author": "Creative Tim",
"license": "Creative Tim License <www.creative-tim.com/license>",
"devDependencies": {
"gulp": "^4.0.0",
"gulp-autoprefixer": "^5.0.0",
"gulp-clean": "^0.4.0",
"gulp-install": "^1.1.0",
"gulp-open": "^3.0.1",
"gulp-sass": "^4.0.1",
"gulp-sourcemaps": "^2.6.4"
}
}
Constantly restoring the backup of the Now-UI-kit folder is quit cumbersome and is error sensitive. I recently started with using package, and for this problem, I'd like to understand how I kan solve the problem. I did do a search on Stackoverflow and found some suggestions which I did try, but no luck yet.
Thanks in advance for your time.

Related

How to make mtd-utils 2.0 for specified deployment path

I downloaded mtd-utils 2.0 and I want to built it for specified deployment path. If I launch:
./configure --bindir .../mtd-utils-81049e5/deploy/usr/sbin
and then I do:
make
I will get output into folder, where I launched make. I want to have executable files somewhere like: bla/mtd-utils-2.0.../deploy/usr/sbin...
IIUC, you can do this like that:
./configure --prefix=/tmp/mtd-utils
make
make install
Finally, you get this:
$ tree /tmp/mtd-utils
/tmp/mtd-utils
├── sbin
│   ├── doc_loadbios
│   ├── docfdisk
│   ├── flash_erase
│   ├── flash_eraseall
│   ├── flash_lock
│   ├── flash_otp_dump
│   ├── flash_otp_info
│   ├── flash_otp_lock
│   ├── flash_otp_write
│   ├── flash_unlock
│   ├── flashcp
│   ├── ftl_check
│   ├── ftl_format
│   ├── jffs2dump
│   ├── jffs2reader
│   ├── mkfs.jffs2
│   ├── mkfs.ubifs
│   ├── mtd_debug
│   ├── mtdinfo
│   ├── mtdpart
│   ├── nanddump
│   ├── nandtest
│   ├── nandwrite
│   ├── nftl_format
│   ├── nftldump
│   ├── recv_image
│   ├── rfddump
│   ├── rfdformat
│   ├── serve_image
│   ├── sumtool
│   ├── ubiattach
│   ├── ubiblock
│   ├── ubicrc32
│   ├── ubidetach
│   ├── ubiformat
│   ├── ubimkvol
│   ├── ubinfo
│   ├── ubinize
│   ├── ubirename
│   ├── ubirmvol
│   ├── ubirsvol
│   └── ubiupdatevol
└── share
└── man
├── man1
│   └── mkfs.jffs2.1
└── man8
└── ubinize.8
5 directories, 44 files

Correct way of starting a NodeJs, React project with Express

I'm beginning with React, NodeJs and ExpressJs. I have seen many tutorials but I'm not sure of the correct way to start a project?
I have seen two ways. The first being express <project_name> and the second being npm init.
Which is correct and if there isn't a correct way then why would you initialize them differently when npm init includes express eventually (In the tutorials).
Thanks
npm init is good way to start, as you know it creates a package.json file in your project directory where you can store your project dependencies.
After this you must run the following commands:
npm install --save-dev webpack
npm install --save-dev babel
npm install --save-dev babel-loader
npm install babel-core
npm install babel-preset-env
npm install babel-preset-react
or as a single line command use this:
npm install --save-dev webpack babel babel-loader babel-core babel-preset-env babel-preset-react
first command will create a webpack.config.js file.
Second command will ready the babel to use in your project and the third to use babel-loader.
Now it's time to create project structure which looks like :
projectFolder/
├── package.json
├── public
│   ├── favicon.ico
│   └── index.html
├── README.md
└── src
├── App.css
├── App.js
├── App.test.js
├── index.css
├── index.js
└── logo.png
This is the very basic project structure. It doesn't have server side structure.
full structure looks like:
react/
├── CHANGELOG.md
├── CONTRIBUTING.md
├── docs
│   ├── data-fetching.md
│   ├── getting-started.md
│   ├── how-to-configure-text-editors.md
│   ├── react-style-guide.md
│   ├── README.md
│   └── recipes/
├── LICENSE.txt
├── node_modules/
├── package.json
├── README.md
├── src
│   ├── actions
│   ├── client.js
│   ├── components
│   │   ├── App
│   │   │   ├── App.js
│   │   │   ├── App.scss
│   │   │   ├── package.json
│   │   │   └── __tests__
│   │   │   └── App-test.js
│   │   ├── ContentPage
│   │   │   ├── ContentPage.js
│   │   │   ├── ContentPage.scss
│   │   │   └── package.json
│   │   ├── ErrorPage
│   │   │   ├── ErrorPage.js
│   │   │   ├── ErrorPage.scss
│   │   │   └── package.json
│   │   ├── Feedback
│   │   │   ├── Feedback.js
│   │   │   ├── Feedback.scss
│   │   │   └── package.json
│   │   ├── Footer
│   │   │   ├── Footer.js
│   │   │   ├── Footer.scss
│   │   │   └── package.json
│   │   ├── Header
│   │   │   ├── Header.js
│   │   │   ├── Header.scss
│   │   │   ├── logo-small#2x.png
│   │   │   ├── logo-small.png
│   │   │   └── package.json
│   │   ├── Link
│   │   │   ├── Link.js
│   │   │   └── package.json
│   │   ├── Navigation
│   │   │   ├── Navigation.js
│   │   │   ├── Navigation.scss
│   │   │   └── package.json
│   │   ├── NotFoundPage
│   │   │   ├── NotFoundPage.js
│   │   │   ├── NotFoundPage.scss
│   │   │   └── package.json
│   │   ├── TextBox
│   │   │   ├── package.json
│   │   │   ├── TextBox.js
│   │   │   └── TextBox.scss
│   │   ├── variables.scss
│   │   └── withViewport.js
│   ├── config.js
│   ├── constants
│   │   └── ActionTypes.js
│   ├── content
│   │   ├── about.jade
│   │   ├── index.jade
│   │   └── privacy.jade
│   ├── core
│   │   ├── db.js
│   │   ├── DOMUtils.js
│   │   ├── fetch
│   │   │   ├── fetch.client.js
│   │   │   ├── fetch.server.js
│   │   │   └── package.json
│   │   ├── Location.js
│   │   └── passport.js
│   ├── data
│   │   ├── queries
│   │   │   ├── content.js
│   │   │   ├── me.js
│   │   │   └── news.js
│   │   ├── schema.js
│   │   └── types
│   │   ├── ContentType.js
│   │   ├── NewsItemType.js
│   │   └── UserType.js
│   ├── public
│   │   ├── apple-touch-icon.png
│   │   ├── browserconfig.xml
│   │   ├── crossdomain.xml
│   │   ├── favicon.ico
│   │   ├── humans.txt
│   │   ├── robots.txt
│   │   ├── tile.png
│   │   └── tile-wide.png
│   ├── routes
│   │   ├── contact
│   │   │   ├── Contact.js
│   │   │   ├── Contact.scss
│   │   │   └── index.js
│   │   ├── home
│   │   │   ├── Home.js
│   │   │   ├── Home.scss
│   │   │   └── index.js
│   │   ├── login
│   │   │   ├── index.js
│   │   │   ├── Login.js
│   │   │   └── Login.scss
│   │   └── register
│   │   ├── index.js
│   │   ├── Register.js
│   │   └── Register.scss
│   ├── routes.js
│   ├── server.js
│   ├── stores
│   └── views
│   ├── error.jade
│   └── index.jade
├── test
│   └── stubs
│   └── SCSSStub.js
└── tools
├── build.js
├── bundle.js
├── clean.js
├── copy.js
├── deploy.js
├── lib
│   ├── fetch.js
│   └── fs.js
├── README.md
├── run.js
├── runServer.js
├── start.js
└── webpack.config.js
Created using yeoman generator-react-fullstack
Alternatively you can do all this stuff by simply using yeoman react generator but be careful with generators, they sometimes toughen your deployment process.

Which directory to put snippets.json file for customization?

Emmet plugin installed on my vim74.
Here are some tutorial from the mannual .
https://docs.emmet.io/customization/snippets/
Create snippets.json file in extensions folder to add or override snippets.
sudo find / -name 'snippets.jsom'
nothing as output.
No snippets.json in my directories,i want to create it as the mannual say,which directory to put it in?
What does extensions folder mean?
Which directory is extensions folder for my vim and emmet?
tree -L 2 /usr/share/vim
/usr/share/vim
├── addons
│   ├── doc
│   └── plugin
├── registry
│   └── vim-runtime.yaml
├── vim74
│   ├── autoload
│   ├── bugreport.vim
│   ├── bundle
│   ├── colors
│   ├── compiler
│   ├── debian.vim
│   ├── delmenu.vim
│   ├── doc
│   ├── evim.vim
│   ├── filetype.vim
│   ├── ftoff.vim
│   ├── ftplugin
│   ├── ftplugin.vim
│   ├── ftplugof.vim
│   ├── gvimrc_example.vim
│   ├── indent
│   ├── indent.vim
│   ├── indoff.vim
│   ├── keymap
│   ├── lang
│   ├── macros
│   ├── menu.vim
│   ├── mswin.vim
│   ├── optwin.vim
│   ├── plugin
│   ├── print
│   ├── rgb.txt
│   ├── scripts.vim
│   ├── spell
│   ├── synmenu.vim
│   ├── syntax
│   ├── tutor
│   └── vimrc_example.vim
├── vimfiles -> /etc/vim
├── vimrc -> /etc/vim/vimrc
└── vimrc.tiny -> /etc/vim/vimrc.tiny
tree -L 1 /usr/share/vim/vim74/autoload
/usr/share/vim/vim74/autoload
├── adacomplete.vim
├── ada.vim
├── ccomplete.vim
├── clojurecomplete.vim
├── csscomplete.vim
├── decada.vim
├── emmet
├── emmet.vim
├── getscript.vim
├── gnat.vim
├── gzip.vim
├── htmlcomplete.vim
├── javascriptcomplete.vim
├── netrwFileHandlers.vim
├── netrw_gitignore.vim
├── netrwSettings.vim
├── netrw.vim
├── paste.vim
├── phpcomplete.vim
├── python3complete.vim
├── pythoncomplete.vim
├── README.txt
├── rubycomplete.vim
├── spellfile.vim
├── sqlcomplete.vim
├── syntaxcomplete.vim
├── tar.vim
├── tohtml.vim
├── vimball.vim
├── xml
├── xmlcomplete.vim
└── zip.vim
2 directories, 30 files
tree -l 1 /usr/share/vim/vim74/plugin
1 [error opening dir]
/usr/share/vim/vim74/plugin
├── emmet.vim
├── getscriptPlugin.vim
├── gzip.vim
├── matchparen.vim
├── netrwPlugin.vim
├── README.txt
├── rrhelper.vim
├── spellfile.vim
├── tarPlugin.vim
├── tohtml.vim
├── vimballPlugin.vim
└── zipPlugin.vim
The linked page says:
Please refer to README file bundled with your editor’s plugin to find out where Emmet looks for extensions.
When you read this sentence, what is the only reasonable thing to do? Reading your plugin's READMEof course! A README that says:
If you have installed the web-api for emmet-vim you can also add your own snippets using a custom snippets.json file.
Once you have installed the web-api add this line to your .vimrc:
let g:user_emmet_settings = webapi#json#decode(join(readfile(expand('~/.snippets_custom.json')), "\n"))
You can change the path to your snippets_custom.json according to your preferences.
1.to install pathogen.vim
mkdir -p ~/.vim/autoload ~/.vim/bundle && \
curl -LSso ~/.vim/autoload/pathogen.vim https://tpo.pe/pathogen.vim
2.to edite snippets.json
copy https://github.com/emmetio/emmet/blob/master/lib/snippets.json and revise something for your customization.
I want to make html:5 expand as below.
<html lang="zh">
<head>
<meta charset="gbk">
<title></title>
</head>
<body>
</body>
</html>
vim ~./vim/snippets.json
"variables": {
"lang": "zh",
"locale": "en-US",
"charset": "gbk",
"indentation": "\t",
"newline": "\n"
},
To list only part codes of it.
3.to edite your .vimrc to call snippets.json
vim .vimrc
let g:user_emmet_settings = webapi#json#decode(join(readfile(expand('~/.vim/snippets.json')), "\n"))

npm install , installs package not even listed in my package.json file

I am new to NodeJS and just cloned the code and checked my node_modules folder which has almost 100's of dependencies installed. This is my directory structure
node_modules/
├── accepts
├── after
│   └── test
├── ansi-regex
├── ansi-styles
├── arraybuffer.slice
│   └── test
├── array-flatten
├── asn1
│   ├── lib
│   │   └── ber
│   └── tst
│   └── ber
├── assert-plus
├── async
│   ├── lib
│   └── support
├── aws-sign2
├── backo2
│   └── test
├── base64-arraybuffer
│   ├── lib
│   └── test
├── base64id
│   └── lib
├── base64-url
├── benchmark
│   ├── doc
│   └── test
├── better-assert
├── bindings
├── bl
│   ├── node_modules
│   │   └── readable-stream
│   │   ├── doc
│   │   │   └── wg-meetings
│   │   └── lib
│   └── test
├── blob
│   └── test
├── bluebird
│   └── js
│   ├── browser
│   └── main
├── body-parser
│   └── lib
│   └── types
├── boom
│   ├── images
│   ├── lib
│   └── test
├── bson
│   ├── alternate_parsers
│   ├── browser_build
│   ├── lib
│   │   └── bson
│   │   └── parser
│   └── tools
├── bufferutil
│   ├── build
│   │   └── Release
│   │   └── obj.target
│   │   └── bufferutil
│   │   └── src
│   └── src
├── bytes
├── callsite
├── caseless
├── chalk
├── combined-stream
│   └── lib
├── commander
├── component-bind
├── component-emitter
├── component-inherit
│   └── test
├── connect-mongodb-session
│   └── test
├── content-disposition
├── content-type
├── cookie
├── cookie-parser
├── cookie-signature
├── core-util-is
│   └── lib
├── crc
│   └── lib
├── cryptiles
│   ├── lib
│   └── test
├── dashdash
│   └── lib
├── debug
├── delayed-stream
│   └── lib
├── depd
│   └── lib
│   ├── browser
│   └── compat
├── destroy
├── ecc-jsbn
│   └── lib
├── ee-first
├── engine.io
│   ├── lib
│   │   └── transports
│   └── node_modules
│   ├── debug
│   └── ms
├── engine.io-client
│   ├── lib
│   │   └── transports
│   └── node_modules
│   ├── debug
│   ├── ms
│   └── parseuri
├── engine.io-parser
│   └── lib
├── es6-promise
│   ├── dist
│   └── lib
│   └── es6-promise
│   └── promise
├── escape-html
├── escape-string-regexp
├── etag
├── express
│   ├── lib
│   │   ├── middleware
│   │   └── router
│   └── node_modules
│   ├── cookie
│   ├── depd
│   │   └── lib
│   │   └── compat
│   └── qs
│   ├── lib
│   └── test
├── express-session
│   ├── node_modules
│   │   └── cookie
│   └── session
├── extend
├── extsprintf
│   ├── examples
│   └── lib
├── finalhandler
├── flushwritable
│   ├── lib
│   └── test
├── forever-agent
├── form-data
│   ├── lib
│   └── node_modules
│   └── async
│   ├── dist
│   └── lib
├── forwarded
├── fresh
├── generate-function
├── generate-object-property
├── global
│   └── test
├── graceful-readlink
├── gridfs-stream
│   ├── lib
│   └── test
│   └── fixtures
├── har-validator
│   ├── bin
│   └── lib
│   └── schemas
├── has-ansi
├── has-binary
│   └── fixtures
├── has-binary-data
│   └── fixtures
├── has-cors
├── hawk
│   ├── dist
│   ├── example
│   ├── images
│   ├── lib
│   └── test
├── hoek
│   ├── images
│   ├── lib
│   └── test
│   └── modules
├── hooks-fixed
├── http-errors
├── http-signature
│   └── lib
├── iconv-lite
│   ├── encodings
│   │   └── tables
│   └── lib
├── indexof
├── inherits
├── ipaddr.js
│   ├── lib
│   ├── src
│   └── test
├── isarray
│   └── build
├── is-my-json-valid
│   └── test
│   ├── fixtures
│   └── json-schema-draft4
├── is-property
├── isstream
├── is-typedarray
├── jodid25519
│   └── lib
├── jsbn
├── json3
│   ├── coverage
│   │   └── lcov-report
│   │   └── lib
│   └── lib
├── jsonpointer
├── json-schema
│   ├── draft-00
│   ├── draft-01
│   ├── draft-02
│   ├── draft-03
│   │   └── examples
│   ├── draft-04
│   ├── lib
│   └── test
├── json-stringify-safe
│   └── test
├── jsprim
│   └── lib
├── kareem
│   └── test
├── lodash
│   ├── array
│   ├── chain
│   ├── collection
│   ├── date
│   ├── function
│   ├── internal
│   ├── lang
│   ├── math
│   ├── number
│   ├── object
│   ├── string
│   └── utility
├── media-typer
├── merge-descriptors
├── methods
├── mime
│   └── build
├── mime-db
├── mime-types
├── moment
│   ├── locale
│   └── min
├── mongodb
│   ├── lib
│   │   ├── bulk
│   │   ├── gridfs
│   │   └── gridfs-stream
│   └── test_boot
│   └── data
│   └── diagnostic.data
├── mongodb-core
│   └── lib
│   ├── auth
│   ├── connection
│   ├── tools
│   ├── topologies
│   │   └── strategies
│   └── wireprotocol
├── mongoose
│   ├── examples
│   │   ├── aggregate
│   │   ├── express
│   │   │   └── connection-sharing
│   │   ├── geospatial
│   │   ├── globalschemas
│   │   ├── lean
│   │   ├── mapreduce
│   │   ├── population
│   │   ├── promises
│   │   ├── querybuilder
│   │   ├── replicasets
│   │   ├── schema
│   │   │   └── storing-schemas-as-json
│   │   └── statics
│   ├── lib
│   │   ├── drivers
│   │   │   ├── browser
│   │   │   └── node-mongodb-native
│   │   ├── error
│   │   ├── schema
│   │   │   └── operators
│   │   ├── services
│   │   └── types
│   └── node_modules
│   ├── async
│   │   └── lib
│   └── bson
│   ├── alternate_parsers
│   ├── browser_build
│   ├── lib
│   │   └── bson
│   │   └── parser
│   └── tools
├── mpath
│   ├── lib
│   └── test
├── mpromise
│   ├── lib
│   └── test
├── mquery
│   ├── lib
│   │   └── collection
│   └── test
│   └── collection
├── ms
├── muri
│   ├── lib
│   └── test
├── nan
│   ├── doc
│   └── tools
├── negotiator
│   └── lib
├── node-gcm
│   ├── lib
│   └── node_modules
│   └── debug
│   └── lib
├── node-uuid
│   ├── benchmark
│   ├── bin
│   └── test
├── oauth
│   ├── examples
│   │   └── express-gdata
│   │   └── views
│   ├── lib
│   └── tests
├── oauth-sign
├── object-component
│   └── test
├── object-keys
├── on-finished
├── on-headers
├── options
│   └── lib
├── parsejson
├── parseqs
├── parseuri
├── parseurl
├── passport
│   └── lib
│   ├── errors
│   ├── framework
│   ├── http
│   ├── middleware
│   └── strategies
├── passport-facebook
│   └── lib
│   └── errors
├── passport-local
│   └── lib
├── passport-oauth2
│   └── lib
│   └── errors
├── passport-strategy
│   └── lib
├── password-hash
│   ├── bin
│   ├── lib
│   └── test
├── path-to-regexp
├── pause
├── pinkie
├── pinkie-promise
├── process-nextick-args
├── proxy-addr
├── qs
│   ├── dist
│   ├── lib
│   └── test
├── random-key
├── range-parser
├── raw-body
├── readable-stream
│   └── lib
├── regexp-clone
│   └── test
├── request
│   └── lib
├── send
│   └── node_modules
│   └── depd
│   └── lib
│   └── compat
├── serve-static
├── sliced
│   ├── lib
│   └── test
├── sntp
│   ├── examples
│   ├── lib
│   └── test
├── socket.io
│   ├── lib
│   └── node_modules
│   ├── debug
│   └── ms
├── socket.io-adapter
│   └── node_modules
│   ├── debug
│   ├── ms
│   └── socket.io-parser
│   ├── bench
│   └── node_modules
│   └── debug
│   └── lib
├── socket.io-client
│   ├── lib
│   └── node_modules
│   └── debug
│   └── lib
├── socket.io-parser
│   ├── bench
│   └── node_modules
│   └── debug
│   └── lib
├── sshpk
│   ├── bin
│   ├── lib
│   │   └── formats
│   └── node_modules
│   └── assert-plus
├── statuses
├── string_decoder
├── stringstream
├── strip-ansi
├── supports-color
├── to-array
├── tough-cookie
│   └── lib
├── tunnel-agent
├── tweetnacl
├── type-is
├── uid2
├── uid-safe
├── ultron
├── unpipe
├── utf8
│   └── tests
├── utf-8-validate
│   ├── build
│   │   └── Release
│   │   └── obj.target
│   │   └── validation
│   │   └── src
│   └── src
├── util-deprecate
├── utils-merge
├── vary
├── verror
│   ├── examples
│   ├── lib
│   └── tests
├── ws
│   └── lib
├── xmlhttprequest
│   ├── example
│   ├── lib
│   └── tests
└── xtend
and this my package.json
{
"name": "my-api",
"version": "1.0.0",
"description": "",
"main": "app.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC",
"dependencies": {
"async": "^0.9.0",
"body-parser": "^1.12.0",
"cookie-parser": "^1.3.4",
"express": "latest",
"express-session": "^1.11.1",
"gridfs-stream": "latest",
"moment": "^2.10.6",
"mongoose": "latest",
"node-gcm": "latest",
"passport": "^0.2.1",
"passport-facebook": "latest",
"passport-local": "latest",
"password-hash": "^1.2.2",
"random-key": "^0.3.2",
"socket.io": "^1.3.5",
"connect-mongodb-session" : "latest"
}
}
What is wrong with it? My friend had the same project but in his node_modules only the folders mentioned in package.json are created.
They're dependencies of dependencies -
Example:
You have a dependency on express.
This in turn, has dependencies on several packages
Each of these have dependencies, on so on...
When you npm install the whole dependency graph needs to be downloaded into your node_modules folder
A nice itneractive tool for visualising the dependency graph of express is http://npm.anvaka.com/#/view/2d/express

laravel default localizations for other languages?

A new Laravel project already comes with some localizations, in english.
.
└── en
├── auth
│   ├── form.php
│   └── message.php
├── button.php
├── general.php
├── groups
│   ├── form.php
│   ├── message.php
│   ├── modal.php
│   ├── table.php
│   └── title.php
├── pagination.php
├── passwords.php
├── reminders.php
├── users
│   ├── message.php
│   ├── modal.php
│   └── title.php
└── validation.php
Are those files available for other languages, too?
Some people have published a few. See for example https://github.com/caouecs/Laravel-lang

Resources