I have been using comments to track the version I am on. Then after every upgrade, I run my test suite. And I separated by deps.ts into a standard import section and a third party section.
I try to be very clear on what version everything is set too. And I am relying on documentation, for now, to try and be very clear.
Example of my deps.ts
/**
* Standard Libraries - Tagged to 0.65.0 for Deno 1.3.0
*/// Assertexport{assert,assertEquals,assertThrows,}from"https://deno.land/std@0.65.0/testing/asserts.ts";// Benchmarksexport{runBenchmarks,bench,}from"https://deno.land/std@0.65.0/testing/bench.ts";// Colorsexport{bold,cyan,green,yellow,red,bgGreen,bgYellow,black,}from"https://deno.land/std@0.65.0/fmt/colors.ts";/**
* Third-Party Libraries
*/// Some Library v1.20export{something}from"https://deno.land/x/something@v1.2.0/mod.ts";
Nice write up.
I have been using comments to track the version I am on. Then after every upgrade, I run my test suite. And I separated by
deps.ts
into a standard import section and a third party section.I try to be very clear on what version everything is set too. And I am relying on documentation, for now, to try and be very clear.
Example of my
deps.ts
yeah pretty cool
be sure to use
--reload
after upgrade to ensure the validity of all the dependencies