Set default stable version for import

[nbbaier]

@RLesser noticed that my hacking away on my SQLite Studio had caused his import of val to start glitching. I managed to rectify this by specifying a "stable version" in the readme, but it would be really nice to have a more official way to do this.

I like Robert's suggestion of specifying a default stable version that automatically imports. The issue I see with this is that it requires some way of notifying users to upgrade to the latest version.

Another option I just thought of would be allowing a ?v=stable param that defaults to the set stable version.

Related to #44

[stevekrouse]

You could copy @saolsen's technique described here and make your active development live on sqlite_studio_dev and then have the main sqlite_studio val look like this:

export { default } from "https://esm.town/v/nbbaier/sqlite_studio_dev?v=37";

export { default as dev } from "https://esm.town/v/nbbaier/sqlite_studio_dev";

export { default as stable } from "https://esm.town/v/nbbaier/sqlite_studio_dev?v=37";

export { default as v2 } from "https://esm.town/v/nbbaier/sqlite_studio_dev?v=20";

In effect you could have the "main val" contain all the tags you care about!