devtools-detect
eslint-config-standard
devtools-detect | eslint-config-standard | |
---|---|---|
8 | 7 | |
2,006 | 2,568 | |
- | 0.8% | |
4.7 | 8.6 | |
8 days ago | 1 day ago | |
HTML | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
devtools-detect
-
Website just displays "Unwanted Dev Tools Console detected "
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."
-
Resizing works in the browser, but doesn't work when 'Inspecting' (more in comments)
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
-
MailChimp blacklists your IP if you open the browser's dev tools
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...
-
Can we prevent the users of our website from accessing web dev tools (of any browser) while they are on our site?
they even imported a 4 year old package to handle devtools detection: https://github.com/sindresorhus/devtools-detect
- Copy text from the websites which don't allow
-
JavaScript Is Weird
Devtools can actually be detected to a certain extent - https://github.com/sindresorhus/devtools-detect
eslint-config-standard
-
PURISTA - Thanks to amazing open-source software
eslint-config-standard
-
Setting up ESLINT with TS/JS in your React project in 2023
Based on your requirements and environment, answer the questions accordingly. At least with eslint version 8.0.1, you are only presented with 2 style guides: standard and XO. Personally, I prefer the standard styling guide but at any give time, it is a personal choice and as such feel free to choose any from a bunch of available options. Once all dependencies are installed, ensure that you have the following packages added as devDependencies to your project:
-
[AskJS] favorite JavaScript library
Hmm right, haven't found too many controversial things in https://github.com/standard/eslint-config-standard/blob/master/.eslintrc.json, besides no-semi fixed by semi-standard and comma-dangle "never" (sucks for git history, they should allow it for multiline cases https://eslint.org/docs/rules/comma-dangle#always-multiline)
-
Some tips on tooling for improving our code
ESLint plugin for StandardJS; allows you to format code as StandardJS, but clear more serious errors too.
-
A notable JavaScript developer shamelessly copied one of my most downloaded nod
The JS Open Source Community is filled with people grifting things like this. Quite notably, there's a linter called JS Standard Style, which actually has nothing to do with JS Standards.
It's marketed as if it was a standard, the fact that it isn't is tucked away in the readme, and also -- the entire project is just a wrapper around someones .eslintrc file, yet barely any credit is given to the ESLint devs who do all the work.
Go ahead and read the readme here, https://github.com/standard/standard. Could you genuinely tell this wasn't really a JS Standard at a glance? Could you tell this was just a config file for someone elses work? None of the donations go upstream to eslint by the way.
Hell, the actual config file is hidden inside a sub repo:
https://github.com/standard/eslint-config-standard
which has the audacity to claim
> This module is for advanced users. You probably want to use standard instead :)
It's a config file for someone elses program! Why does this library go through so much effort to hide that it's just someones config file? Why on earth is it called JS Standard Style?
The whole community is filled with slimy nonsense like this.
-
JavaScript Is Weird
Eslint is the default linter. Standard is a curated list of rules with good quality.
https://github.com/standard/eslint-config-standard
I would start with that and tweak what you don't like
-
Getting Started with Next.js - VSCode, ESLint and Prettier
Well done, we managed to set up ESLint using Airbnb’s JavaScript styling guide to our newly created Next.js project. You could have used another popular styling guide like Google, Standard, or even create your own to your liking.
What are some alternatives?
V7 - Embedded JavaScript engine for C/C++
prettier - Prettier is an opinionated code formatter.
proposal-pattern-matching - Pattern matching syntax for ECMAScript
standard - Ruby's bikeshed-proof linter and formatter 🚲
proposal-slice-notation
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
decimal.js - An arbitrary-precision Decimal type for JavaScript
success-symbol - Cross-platform success symbol.
bhai-lang - A toy programming language written in Typescript
nanocolors - Use picocolors instead. It is 3 times smaller and 50% faster.
ansi-reset - The color reset, in ansi.
ESLint - Find and fix problems in your JavaScript code.