You missed `deno outdated` which can be used to list all outdated deps and can be updated to the latest versions using `deno outdated --update --latest`. Also, the new improvements to `deno task` are so so good!
not a silly question! you can do both :) you can use URL imports for smaller projects / scripts and deno install/package manager for larger projects/teams. URL imports are great because your projects can simply be a single file without a dependency manifest or anything else.
@@deno_land yup love the simplicity of the link imports, already started migrating my projects to deno and deno deploy ✨ if you dont mind can you please give a couple of examples of where the import/install would be a good idea, the whole teams/big project thing isnt sitting right with me as in my brain wouldnt not having to deal with dependencies be easier in a big team or project? Not sure if you get what i mean haha, but ya thank you for the reply, love simple systems love whats deno is doing. Also on a slight tangent i really wish that when u make a fresh fresh project and pick tailwind css it would just use the cdn instead of making a node module folders, it clutters what would else be a very clean file directory, not sure if that can be a flag or an option.
You missed `deno outdated` which can be used to list all outdated deps and can be updated to the latest versions using `deno outdated --update --latest`.
Also, the new improvements to `deno task` are so so good!
we're gonna do another video to cover those!
This might be a silly question, but wasnt the whole point to not have dependencies installed? Like u can just reference by link?
They made fun of package.json and added it back again lol
It has to live somewhere in disk unless you want to download it all and keep it memory until next rub
not a silly question! you can do both :) you can use URL imports for smaller projects / scripts and deno install/package manager for larger projects/teams. URL imports are great because your projects can simply be a single file without a dependency manifest or anything else.
@@deno_land yup love the simplicity of the link imports, already started migrating my projects to deno and deno deploy ✨ if you dont mind can you please give a couple of examples of where the import/install would be a good idea, the whole teams/big project thing isnt sitting right with me as in my brain wouldnt not having to deal with dependencies be easier in a big team or project? Not sure if you get what i mean haha, but ya thank you for the reply, love simple systems love whats deno is doing.
Also on a slight tangent i really wish that when u make a fresh fresh project and pick tailwind css it would just use the cdn instead of making a node module folders, it clutters what would else be a very clean file directory, not sure if that can be a flag or an option.
no info on update or info but the title card implied?
Love it