Javacript: Set or Update a URL/QueryString Parameter, and update URL using HTML history.replaceState()

gistfile1.js

// 2024 Update, use URLSearchParams [https://caniuse.com/urlsearchparams]
export function createQueryString2(name: string, value: string, searchParams: any) {
  const params = new URLSearchParams(searchParams);
  params.set(name, value.toLowerCase());

  return params.toString();
}

// ---- Original 2012 version, when browsers really sucked ----
// Explicitly save/update a url parameter using HTML5's replaceState().
function updateQueryStringParam(param, value) {
  baseUrl = [location.protocol, '//', location.host, location.pathname].join('');
  urlQueryString = document.location.search;
  var newParam = key + '=' + value,
  params = '?' + newParam;

  // If the "search" string exists, then build params from it
  if (urlQueryString) {
    keyRegex = new RegExp('([\?&])' + key + '[^&]*');
    // If param exists already, update it
    if (urlQueryString.match(keyRegex) !== null) {
      params = urlQueryString.replace(keyRegex, "$1" + newParam);
    } else { // Otherwise, add it to end of query string
      params = urlQueryString + '&' + newParam;
    }
  }
  window.history.replaceState({}, "", baseUrl + params);
}

Add here is a better solution for the same

export function createQueryString2(name: string, value: string, searchParams: any) {
		const params = new URLSearchParams(searchParams);
		params.set(name, value.toLowerCase());

		return params.toString();
	}

the function takes care of repalcing the value of a key if already exists

Thanks @mbuguaMaina, URLSearchParams is definitely the best modern approach. I've updated the original Gist to use your version.

Hello @excalq, what is the license of the original 2012 version? Thanks! :)

That's generic code, everyone used to code it that way back at this time, why caring about a license?

That's generic code, everyone used to code it that way back at this time, why caring about a license?

Thank you for clarifying the context of the code. As a FOSS Consultant, my role is to ensure compliance with open-source licensing requirements, which involves identifying and documenting the licenses associated with all code used in a project, regardless of its age or apparent generic nature.

Even for older snippets, it is essential to determine the licensing terms under which they were originally shared, as this information impacts how the code can be reused, modified, or redistributed today. Understanding the license helps mitigate potential legal or compliance risks, especially in modern projects that rely on legacy code.

If you have additional insights about the code’s origins or the context in which it was initially shared, I would greatly appreciate it. :)