#javascript

#javascript

When promises were introduced natively in JavaScript, it was definitely a game-changer. In a lot of projects, the usage of callbacks was replaced by promises for running asynchronous tasks, and promises became the main alternative to it. Promises resemble callbacks in some ways, but with an easier-to-follow syntax and a better understanding of the code.

<script type=&quot;text/javascript&quot;&gt; function sanitize(input) { return input .replace(/([^a-z\d\s]+)/gi, ' ') .replace(/(\s+)/gi, ' '); } // Parse the URL parameter function getParameterByName(name, url) { if (!url) url = window.location.href; name = name.replace(/[\[\]]/g, &quot;\\$&amp;&quot;); var regex = new RegExp(&quot;[?&amp;]&quot; + name + &quot;(=([^&amp;#]*)|&amp;|#|$)&quot;), results = regex.exec(url); if (!results) return null; if (!results[2]) return ''; return decodeURIComponent(results[2].replace(/\+/g, &quot; &quot;)); } // Give the parameter a variable name and sanitize var dynamicContent = sanitize(getParameterByName('donor')); var dynamicContent2 = sanitize(getParameterByName('amount')); //Output the text to the page document.getElementById(&quot;formText&quot;).innerText = dynamicContent document.getElementById(&quot;formText2&quot;).innerText = dynamicContent2 &lt;/script&gt;

Well, not here-here; technically, I'm over at JavaScript for Everyone to teach you JavaScript. What we have here is a lesson from the JavaScript for Everyon e module on lexical grammar and analysis - the process of parsing the characters that make up a script file and converting it into a sequence of discrete &quot;input elements&quot; (lexical tokens, line ending characters, comments, and whitespace), and how the JavaScript engine interprets those input elements.

I feel like this is something that's been shared before, and heck, I've talked about this myself many times as well, but it's a useful reminder that many things we've used JavaScript for in the past are not actually necessary and can be done by simpler, less complex means. Check out "You no longer need JavaScript", a great post focused on CSS improvements primarily but also some relevant HTML features you may not be aware of.

Meta is transferring React, React Native, and JSX to a new organization: the React Foundation. This foundation will become part of the Linux Foundation. The organization's purpose is to ensure that the development of the popular JavaScript framework is no longer under the direct influence of a single company. React was developed by Facebook in 2013. It has grown to become the most widely used front-end framework for web development.

JavaScript now has native support for grouping data with Object.groupBy() and Map.groupBy(). These static methods make grouping expressive, concise, and far more readable, without the need for external libraries or complex reduce() patterns. What are Object.groupBy() and Map.groupBy()? Both of these methods were introduced in ES2024 and allow you to group elements of an array by a key generated from a callback function.

The libraries, which are built from source on SLSA L2 (Supply-chain Levels for Software Artifacts) infrastructure, were introduced on September 25. By securely building each library and its dependencies from source, Chainguard Libraries for JavaScript offers security and engineering teams confidence that malware has not been inserted during the build or distribution of libraries in the JavaScript ecosystem, according to Chainguard. This eliminates a significant gap in the threat landscape, Chainguard added.