amilajack / babel-plugin-fail-explicit Goto Github PK

Example

const some = {}
const { foo } = some
// ^^^ Fails silently

Transformation

const some = {}
const foo = safePropertyAccess(['foo'], some)
// TypeError: Property "foo" does not exist in "Object"

Not 100% sure what the code's intention is, but I think you want to apply it only to operations like +, -, *, ..., but not apply it to comparisons.

I would definitely rather whitelist the supported operators than blacklisting the unsupported ones, since there is a real chance you miss something or tomorrow someone adds a new operator that breaks stuff.

Consider '<', for instance. It's also a comparison, but maybe I missed your intention here 😉

The user should not have to see the stack trace of the plugin. This should be removed

This issue provides visibility into Renovate updates and their statuses. Learn more

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update babel monorepo (@babel/cli, @babel/core, @babel/helper-module-imports, @babel/plugin-transform-modules-commonjs, @babel/plugin-transform-modules-umd, @babel/plugin-transform-runtime, @babel/preset-env, @babel/preset-flow, @babel/traverse, @babel/types)
• Update dependency eslint-config-bliss to ^4.8.1
• Update dependency flow-bin to ^0.174.1
• Update dependency flow-typed to ^3.7.0
• Update Node.js to v16
• Update dependency eslint to v8
• Update dependency eslint-config-bliss to v6
• Update dependency jest to v27
• Click on this checkbox to rebase all open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[2].node' should be a json object, Invalid configuration option: author, Invalid configuration option: babel, Invalid configuration option: bugs, Invalid configuration option: engineStrict, Invalid configuration option: eslintConfig, Invalid configuration option: files, Invalid configuration option: homepage, Invalid configuration option: jest, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: main, Invalid configuration option: name, Invalid configuration option: packageRules[0].@babel/helper-module-imports, Invalid configuration option: packageRules[0].safe-access-check, Invalid configuration option: packageRules[1].@babel/cli, Invalid configuration option: packageRules[1].@babel/core, Invalid configuration option: packageRules[1].@babel/plugin-transform-modules-commonjs, Invalid configuration option: packageRules[1].@babel/plugin-transform-modules-umd, Invalid configuration option: packageRules[1].@babel/plugin-transform-runtime, Invalid configuration option: packageRules[1].@babel/preset-env, Invalid configuration option: packageRules[1].@babel/preset-flow, Invalid configuration option: packageRules[1].@babel/traverse, Invalid configuration option: packageRules[1].@babel/types, Invalid configuration option: packageRules[1].babel-eslint, Invalid configuration option: packageRules[1].babel-plugin-add-module-exports, Invalid configuration option: packageRules[1].babel-plugin-transform-async-to-bluebird, Invalid configuration option: packageRules[1].babel-plugin-transform-promise-to-bluebird, Invalid configuration option: packageRules[1].cross-env, Invalid configuration option: packageRules[1].eslint, Invalid configuration option: packageRules[1].eslint-config-bliss, Invalid configuration option: packageRules[1].flow-bin, Invalid configuration option: packageRules[1].flow-typed, Invalid configuration option: packageRules[1].jest, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version, The "node" object can only be configured at the top level of a config but was found inside "packageRules[2]"

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2015 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2015's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

I have no idea how to do this because I never used coveralls before 😢 Would really appreciate some help with this 😄

Write tests that evaluate the generated code and check for TypError's

safeCoerce -> _safeCoerce. Helps avoid possible naming collisions

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2015 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2015's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]