Scratch JS is a Chrome extension by richgilbank. It had 26,193+ weekly active users and an average rating of 4.40 before it was removed from Chrome Web Store a year ago. Scratch JS is similar to Redux DevTools and AngularJS Batarang. The last published version was 0.0.25, updated 4 years ago.
This extension was removed from Chrome Web Store on
This extension is an add-on for DevTools which integrates both the Traceur and Babel transpilers, allowing you to test out the new JS features coming with ECMAScript 6, also known as ES6 or ES2015. It also supports CoffeeScript, LiveScript and more compile-to-JS languages will be added soon.
Please report issues here:
Scratch JS requires some risky permissions. Exercise caution when installing this extension.
Review carefully before installing.
Risk impact measures the level of extra permissions an extension has access to. A low risk impact
extension cannot do much harms, whereas a high risk impact extension can do a lot of damage like
stealing your password, bypass your security settings, and access your personal data. High risk
impact extensions are not necessarily malicious. However, if they do turn
malicious, they can be very harmful.
Scratch JS may not be trust-worthy. Avoid installing if possible unless you really trust
Risk likelihood measures the probability that a Chrome extension may turn malicious.
This is determined by the publisher and the Chrome extension reputation on Chrome Web Store,
the amount of time the Chrome extension has been around, and other signals about the
Chrome extension. Our algorithms are not perfect, and are subject to change as we
discover new ways to detect malicious extensions. We recommend that you always exercise caution
when installing a Chrome extension, especially ones with higher risk impact and/or
higher risk likelihood.
VM111:1 Refused to load the script 'chrome-extension://alploljligeomonipppgaahpkenfnfkn/node_modules/babel-polyfill/dist/polyfill.min.js' because it violates the following Content Security Policy directive: "script-src chrome://resources chrome://test 'self' 'unsafe-inline' https:". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.