How about move sass-listen to dev dependencies?
See original GitHub issueIf I update sass then it comes with heavy dependencies when I build docker image.
Will it be better to make sass-listen as spec.add_development_dependency
?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Move a module from devDependencies to dependencies in ...
Shorthand to move from devDependencies to dependencies (prod): npm i <module_name> -P. If you want to do the opposite (i.e. move a module ......
Read more >Jekyll: sass-listen-4.0.0 revealed dependencies not in the API ...
I can successfully build and run jekyll but on gitlab the build job fails with Downloading sass-listen-4.0.0 revealed dependencies not in ...
Read more >Adding dependencies to a package.json file - npm Docs
To specify the packages your project depends on, you must list them as "dependencies" or "devDependencies" in your package's package.json file.
Read more >Getting Started on Heroku with Rails 5.x
Runtime dependencies on development/test gems. If you're missing a gem when you deploy, check your Bundler groups. Heroku builds your app ...
Read more >Ruby "there are no ebuilds to satisfy ... - Gentoo Forums :: View topic
(dependency required by "dev-lang/ruby-2.5.5::gentoo" [ebuild]) ... on --verbose-conflicts, fix the xorg-server problem, and then move to the ruby problem.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Dev dependencies are for packages that are only needed when developing the package.
sass-listen
is needed at runtime, to support the--watch
feature.Or would it be nice to separate sass base functionality and sass-cli to separate gems? For example
sass-core
just contain a compiler, that can be used by other frameworks (like rails), andsass
will usesass-core
and contain all goodnesses for command line development.Currently I locked it to version
3.4.25
, because otherwise docker image will become completely blown in size with unnecessary dependencies.