JSLint VS JS-Beautifier

Launched as one of the first linting tools for JavaScript, JSLint is known for being the forefather of JavaScript linters. It is highly opinionated and does not support custom rule configuration, setting a strict coding standard without room for deviation.

This is the spec for the language Douglas Crockford (author of the book "JavaScript: The Good Parts", the JSON specification[1], JSLint[2]) had explained in his famous talk: "The Next Programming Language"[3].

The "big things" in the language are the Actor model, favouring immutability and capabilities-based security.

[1] https://en.wikipedia.org/wiki/JSON

[2] https://www.jslint.com/

[3] https://www.youtube.com/watch?v=R2idkNdKqpQ

Someone should write a book about this [0] and a tool to automate checking your JavaScript code [1].

[0]: https://www.oreilly.com/library/view/javascript-the-good/978...

[1]: https://www.jslint.com/

I'm working on a book called "How to not get your knickers in a twist because you neglected to learn from people who came before you."

JavaScript Linter

One way to achieve this is by using linting tools like ESLint or JSLint. These tools automatically analyze your code for errors, stylistic inconsistencies, and potential security vulnerabilities. By customizing the linting rules to align with coding standards and best practices, you can identify and rectify potential security issues early in the development process. Linting helps maintain a clean and secure codebase.

>Does this mean that in theory i could skip the build/bundling step entirely?

You can but you must write your app in something the browser understands (js not ts, css not sass etc) and use native modules. For example, here is the test harness for a custom module, written in pure html with no build step: https://github.com/javajosh/simpatico/blob/master/combine2.h.... Here is a more complex (and much older) example from Crockford: https://www.jslint.com/

And yes, the experience developing this way is quite nice!

I came across a problem where I had to find the ES6 features used by any javascript project and other data regarding their use. When I reached out to stackoverflow, I could find only one relevant post which asks you to use linters like jshint/jshint or compilers like babel. Jslint didn't seem to report anything specific to ES6 and Babel converts all the ES6+ features to ES5 but doesn't report anything regarding which constructs were used or how many times they were used. However, Jshint reported all ES6 features used in the code along with some metadata. And, to suit my needs, I ended up writing a python script that calls Jshint on all JS files in a project and presents the features used in the project and the number of times they were used across all files. You can find the code here : jsHintRunner

Javascript Linting parses and checks if any syntax is violating the rule. If a violation occurs, a warning is shown explaining unexpected behavior. Use the online version for small projects: JSLint, ESLint or JSHint. For larger projects, it is recommended to use a task runner like Gulp or Grunt. Linters ensure developers are following the best practices as a result of which few bugs appear during project development.

Programmers of classical languages hate JavaScript because it's prototype-based, dynamic and weakly typed (among other complaints). It's also the number one most in-demand programming language in 2022 according to a number of independent surveys. JSLint can help you write better JavaScript and JSMin can minify your code before deployment. These tools were created by Douglas Crockford. I would recommend his books JavaScript: The Good Parts for programmers coming to JavaScript for the first time, and How JavaScript Works for experienced JavaScript programmers.

Even without tools it looked a bit weird, all files in source without minification costs us 27k, its something not needed inside, and if you unpack it with something like https://beautifier.io/ you will see:

I can go through the functions that I have wrote in here. Go to js beautifier and paste in the code for easier viewing while reading this.

I just cobbled together a version using js-beautify https://github.com/beautify-web/js-beautify, works for JavaScript and JSON, does not format HTML correctly.

View source and get the main javascript file https://musicforprogramming.net/client/client.bc21fa59.js then stick it in a beautifier https://beautifier.io/ then grab the most likely looking function, the easiest way is to delete everything that's obviously nothing to do with the animation, then what you have left is the code you want.

One that is customizable, I don't know. Always used vscode formatter with default settings (are there some options?) Or prettier. Maybe https://github.com/beautify-web/js-beautify

Sprite list from the randomizer can be found at https://alttpr.com/sprites/ with links to the zspr files (copy/paste the output into https://beautifier.io/ to make it more readable)

You can use an online service like beautifier.io to try to clean it up a bit. There is no way to get the original human readable JS back though. If you are interested in reading source code, you might have more luck looking at repos on GitHub, which will not be minified.

This is fantastic, thank you for the decoded output. I had run it through Beautifier.io to get some of the unicode/hex characters decoded, but this is much more readable.