need a way to get deno_std version of current Deno

[axetroy]

$ deno --version
deno: 0.24.0
v8: 8.0.192
typescript: 3.7.2
std: 0.23.0

console.log(Deno.versions);

/*
{
  "deno": "0.24.0",
  "v8": "8.0.192",
  "typescript": "3.7.2",
  "std": "0.23.0"
}
*/

deno/cli/js/version.ts

Lines 2 to 6 in c6bb3d5

	interface Version {
	deno: string;
	v8: string;
	typescript: string;
	}

deno/cli/flags.rs

Lines 15 to 19 in c6bb3d5

	macro_rules! std_url {
	($x:expr) => {
	concat!("https://deno.land/[email protected]/", $x)
	};
	}

[ry]

I think std version is confusing to users...

Also I will be removing the "v8" and "typescript" parts of the output in #3389.

[axetroy]

Even if it is not output on the command line, it should be exported in Deno.versions

This is to facilitate future tool integration.

eg. third-party tools use deno install

It can know the version of std for current Deno version, and download the dependencies in advance.

[nayeemrmn]

Even if it is not output on the command line, it should be exported in Deno.versions

But it's only applicable on the command line... I think we just need to figure out how to make the versions align again.

[Fenzland]

You may both import [email protected], [email protected] in your file and run with deno 0.25. So I think a std version in deno --version output is meaningless.

[ry]

reopening. See #3446

[rsp]

You may both import [email protected], [email protected] in your file and run with deno 0.25. So I think a std version in deno --version output is meaningless.

@Fenzland, yes I can import old versions of std in newer runtimes, but is all of the Deno API that is used by all of std modules guaranteed to be backwards compatible? This is not a rhetorical question, it would be good to know if old std versions will continue working with all new versions of Deno, or the other way around, or none of the above. This is a strategic decision for @ry to consider, not a simple one, as I tried to explain in #3320.

[axetroy]

I think this item is outdated

close