Closed shelldandy closed 6 years ago
Another great point!
I think we should ditch bower all together and use NPM only.
Whatcha think @mike3run ?
Well I'm of the opinion that i like having bower since there you can quickly see only the packages you want to use without them getting lost on the endless stuff on the node_modules
folder.
The way I see it is use npm for all logic stuff (compilers, languages, logic) and bower for everything front-end related. Besides not all of the frontend packages are packaged correctly to be super modular (ie: to require them with JS or Sass)
Anyways whatever solution you choose its still wise to do the following:
assets
task that copies thing from one place to another (for example font files, videos, documents, random images, etc)config.js
file where you can wire those together. (That's also useful for sass includes and JS files to concatenate)That way for example you can use bower or npm or whatever and for example if inside the folder there are fonts that you need in your project you just add them to your config.js file without the need to actually copy them manually.
Here's my example config.js file: https://github.com/mike3run/ground-zero/blob/master/gulp/config.js
And here are some gulp tasks i use on a daily basis that are battle tested and really optimized: https://github.com/mike3run/ground-zero/tree/master/gulp/tasks
I noticed that when you tick the option to install neat and bourbon they are not installed with bower instead a local copy is made in a fake bower folder.
That is bad practice since we don't mantain those packages thats what bower or npm are for 😄