devtools-detect VS proposal-slice-notation

For me it's "Sorry,, You can not view this website when JaveScript is disabled, Thank you" I have JavaScript enabled. Looking at the website's HTML source code a lot of logic seems (bad) copy&pasted from other wordpress plugins. For example there's logic that disables right-click, too.

> import devtools from 'https://www.dinbyggare.se/wp-content/plugins/wccp-pro/index....

That's version 2.1 of https://github.com/sindresorhus/devtools-detect Meanwhile version 4 was released and even the maintainer writes "This package has a lot of flaws. It used to work better, but browsers changed, and the detection now has too many false-positives."

My boss has been nagging my co-worker to fix the same issue. Not sure he's attempted implementing it yet, but I recently sent this to my co-worker, so that he can hopefully implement custom code when DevTools are open. https://github.com/sindresorhus/devtools-detect

Looking at the code[0], it just defines an aspect ratio threshold for your browser's viewport and triggers if it's outside of that on width or height. So when you open a second panel, your viewport goes back to being closer to 16:9/16:10 and the tool considers that within both thresholds.

The detection is hilariously primitive and entirely unreliable.

[0]: https://github.com/sindresorhus/devtools-detect/blob/main/in...

they even imported a 4 year old package to handle devtools detection: https://github.com/sindresorhus/devtools-detect

Devtools can actually be detected to a certain extent - https://github.com/sindresorhus/devtools-detect

> Switch statements

JS has had switch statements for a long time. Do you mean switch "expressions" that can be used inline? It's not pretty but JS has long supported that too using either eval() "hacks" or IIFEs: https://stackoverflow.com/questions/32451049/is-eval-the-onl...

Do you mean pattern matching? There are two Stage 1 TC39 proposals with different approaches to it:

More hands-on/direct: https://github.com/tc39/proposal-pattern-matching

More indirect: https://github.com/tc39/proposal-do-expressions

> list comprehensions

There are several libraries with strong Iterator support today that while not syntactically gorgeous do great jobs at allowing you to write simple list operations. Off the top of my head are IxJS and iter-tools, but also classic mainstays like up to date versions of lodash and Ramda.

There's a Stage 2 proposal to bring more of them into "the standard library": https://github.com/tc39/proposal-iterator-helpers

There's also a Stage 2 proposal for an operator to make the syntax generally nicer no matter the library: https://github.com/tc39/proposal-pipeline-operator

> array slicing

Array.prototype.slice() was added back in ES2015: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Array.prototype.at() was "just added" in ES2022 for unary "slice" (ability to use negative indexes): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

If you prefer syntax to function calls, there's a Stage 1 proposal still live for that: https://github.com/tc39/proposal-slice-notation

> better equality operators

That ship has probably sailed. Most projects at this point just have linter rules to standardize everything to the more reliable "triple equals" (===, and !==).

There are proposals for more structural equality functions in the standard library, though, for instance: https://github.com/tc39/proposal-array-equality

Both are stage 1 proposals that I hope get in there some day.

https://github.com/tc39/proposal-slice-notation

https://github.com/tc39/proposal-pattern-matching