You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cd /tmp
$ rails -v
Rails 6.0.3.2
$ rails new my-app
Using -T -d postgresql from /Users/rileytg/.railsrc # use postgres, dont use tests (usually add rspec). this is a fairly common rails stack.
...
Bundle complete! 14 Gemfile dependencies, 65 gems now installed.
...
Installing all JavaScript dependencies [4.2.2]
run yarn add @rails/webpacker@4.2.2 from "."
...
β¨ Done in 17.36s.
Installing dev server for live reloading
run yarn add --dev webpack-dev-server from "."
...
β¨ Done in 8.24s.
Webpacker successfully installed π π°
$ cd my-app/
$ du -h -d 1
60K ./app
32K ./bin π§
120K ./config π§
106M ./node_modules π§π§π§π§π§π§π§π§π§π§π§π§π§
0B ./storage π§
16K ./public π§
0B ./lib
4.0K ./db
0B ./log
72K ./.git
27M ./tmp
0B ./vendor
134M .
Basically several compilers are bundled (node sass, webpack and Babel) so that you don't have to download them as a user and their version is stable for the app. You can use a tool like pnpm to only ever have one copy of them on your system but these aren't deps that negativity impact the app.
YES, this exzessive module junk is driving me crazy!
Why does one need to create a node module for every 30 lines of micro-functionality js?
One should write a checker and if there's more content in .dotfiles and other junky definition files the module creation (node-module upload) should be denied.
Basically several compilers are bundled (node sass, webpack and Babel) so that you don't have to download them as a user and their version is stable for the app. You can use a tool like pnpm to only ever have one copy of them on your system but these aren't deps that negativity impact the app.