Proposal: add origin global

[oles]

It seems there's a miss match between the implementation of origin and/or globalThis.origin and lib.dom.d.ts

$ deno eval "console.log(origin)"
error: Uncaught (in promise) ReferenceError: origin is not defined
console.log(origin)

location works as expected when a --location is and isn't specified

$ deno eval --location=http://localhost:3000 "console.log(location)"
Location {
  hash: "",
  host: "localhost:3000",
  hostname: "localhost",
  href: "http://localhost:3000/",
  origin: "http://localhost:3000",
  pathname: "/",
  port: "3000",
  protocol: "http:",
  search: ""
}

$ deno eval "console.log(location)"
undefined

But it doesn't fix the issue with origin if you do

$ deno eval --location=http://localhost:3000 "console.log(origin)"
error: Uncaught (in promise) ReferenceError: origin is not defined
console.log(origin)

---

$ deno --version
deno 1.44.1 (release, x86_64-unknown-linux-gnu)
v8 12.6.228.3
typescript 5.4.5

[bartlomieju]

That's correct, origin is not an available global. Not everything that is defined in lib.dom.d.ts is available in Deno - eg. document is not available either. What use case do you have for origin?

[oles]

I see, thanks for the clarification!

I had an issue where, after a refactor, an origin variable got lost, and I didn't notice until I ran my test.
I didn't know that origin was a global, and I didn't expect it to cause Deno to throw an error.

---

Side-note:

Having an easy way to get the origin is handy though, and using globalThis.location.origin/location.origin to get it is fine when globalThis.origin/origin isn't possible/supported yet.

I'd ideally like to configure the --location from a .env file though 🤔

[oles]

For anyone else experiencing a similar issue - I found the no-undef deno_lint rule to be very useful.