Deno: Implicitly using master branch Warning should log file

[brandonkal]

This would make locating the offending import much easier.

[hayd]

This could also be solved with external tools e.g. https://github.com/hayd/deno-udd/issues/2

I don't think deno itself should have an opinion on url versioning behavior...

[SyrupThinker]

Also this issue for the deno.land website.

[lucacasonato]

I don't think deno itself should have an opinion on url versioning behavior...

Deno doesn't. It just displays the contents of X-Deno-Warning when it is provided in a response.

[brandonkal]

I don't think deno itself should have an opinion on url versioning behavior...

I tend to agree but unfortunately the CLI already has such an opinion.

It logs

Warning Implicitly using master branch https://offendingimport.com/mod.tsx

Which isn't very useful because this import could be in any number of files.

Deno doesn't. It just displays the contents of X-Deno-Warning when it is provided in a response.

Okay that makes more sense. So this may be a deno_website2 issue. But it would be nice to have some method in the CLI to debug which module requested the file that returns the X-Deno-Warning header. Same for 404 etc.

[lucacasonato]

I agree a sort of stack trace for the import would be nice.

[SyrupThinker]

I agree a sort of stack trace for the import would be nice.

That would be part of #5419

[lucacasonato]

Just talked with @bartlomieju about this, and we came to the conclusion that the warning should be logged on every program start.