Query Parameters in JavaScript (3+1 Ways) 

That cool inline evaluation thing is called *Quokka* quokka.devtipsshow.com

Instead of creating an `` element, you could use `new URLSearchParams(window.location.search)`. Also in node you could require the `url` lib and use it with `URLSearchParams` or `URL`. If you don't want to split the string yourself you could initialize an `URL` and then access the `url.search` for the search string, or `searchParams` for access the interface of `URLSearchParams`.

You're a treasure David.

Why not just use the new Url() ??? This 3 ways look like walking over the sea to get water

Splitting the new URL on the question mark in the 3rd example seemed like a quick solution (although one I'd probably use myself) rather than rebuild the URL from the location.protocol, host and pathname parts. Still, all these options work so it's all good. :-)

Eeyyy new intro! Now some sound effects please! :)

Hey quick question, what's the name of the VSCode extension that it tells you the value / type etc. of an element or variable when you do //? ? Thanks in advance :D

Good to know the good ways of querying those params, thanks lel

God, the muar from your sweater is painful.)))

I knew this wouldn't have the real JavaScript solution as soon as I saw `const URL`. Best JavaScript solution: const url = new URL('...'); url.searchParams.delete('gclid'); Done.

I created a js micro library for parameter manipulation. Helped me a bunch on some recent projects... github.com/samb97/pram.js

hej monika XDD

Can you also teach how we design our own query parameters?

Nice

How about this? You can extract anything after. const url = "test.domain?filter=hardcover&gclid=" const params = new Object() url .split("?")[1] .split("&") .forEach(param => { const [key, value] = param.split("=") params[key] = value }) console.log(params["filter"])

Not sure if it fits this channel, but perhaps working with node.js and some websockets. Or perhaps building your own npm module

wow man you are a genius

Why not just use the new Url() ??? This 3 ways look like walking over the sea to get water

I just learned this for the first time earlier today! Mere coincidence, I think not!

Each time I needed query params to be allowed in the URL I've always used ?something=value. However, few months ago I needed to convert a JSON object into a query parameter to be passed in the URL and my colleague asked me why would I use such technique to pass the object in the URL rather than having a stringified JSON object pasted in the URL directly. Whilst this sound very ugly to me I could not really provide him an answer more than that most websites pass parameters in the url with ?something=value. What would be the drawback to have example.com/'{"something":"value"}" over the more common practise of ?something=value ?

great solution using DOM API (y)

why does a.search only produce what's after the ? mark

keep on hacking :D

How are getting variable values inline in your code?