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: Invalid configuration option: author, Invalid configuration option: binary, Invalid configuration option: bugs, Invalid configuration option: eslintConfig, Invalid configuration option: files, Invalid configuration option: jest, Invalid configuration option: license, Invalid configuration option: main, Invalid configuration option: name, Invalid configuration option: packageRules[0].neon-cli, Invalid configuration option: packageRules[0].node-pre-gyp, Invalid configuration option: packageRules[0].node-pre-gyp-github, Invalid configuration option: packageRules[1].eslint, Invalid configuration option: packageRules[1].eslint-config-bliss, Invalid configuration option: packageRules[1].jest, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version

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

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• fix(deps): update dependency neon-cli to ^0.10.0
• fix(deps): update rust crate diskus to 0.7.0
• chore(deps): update actions/checkout action to v3
• chore(deps): update actions/setup-node action to v3
• chore(deps): update dependency eslint-config-bliss to v6

Open

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

• chore(deps): update dependency eslint to ^7.32.0
• chore(deps): update rust crate neon-build to 0.10.0
• fix(deps): update rust crate neon to 0.10.0
• chore(deps): update dependency eslint to v8
• chore(deps): 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

Waiting on sharkdp/diskus#12

package.json references a main branch version of node-pre-gyp than the modified github:amilajack/node-pre-gyp#neon-compat that has been previously used for neon package publishing.

Running npm run package on this example project only bundles the native directory. There installing the package fails with no access to index.js

Both node-pre-gyp and @mapbox/node-pre-gyp appear to ignore the files section of package.json for files to bundle in the package and I'm struggling to find some documentation for node-pre-gyp that details how to overcome this.

Publish *.node files to different machine architectures

When installing these neon npm modules, either your disk-utility or my ssb-neon-keys, both give an error upon npm install that looks like this:

➜ npm i

> [email protected] install /home/staltz/oss/someproject/node_modules/disk-utility
> node-pre-gyp install --fallback-to-build=false || neon build --release

sh: 1: node-pre-gyp: not found
neon ERR! Command failed: cargo metadata --format-version=1 --no-deps
error: could not find `Cargo.toml` in `/home/staltz/oss/someproject/node_modules/disk-utility/native` or any parent directory

or

➜  npm i

> [email protected] postinstall /home/staltz/oss/someproject/node_modules/ssb-neon-keys
> node-pre-gyp install --fallback-to-build=false || neon build --release

sh: 1: node-pre-gyp: not found
neon ERR! spawn cargo ENOENT

Error: spawn cargo ENOENT

This seems to be the case regardless if node-pre-gyp is defined in package.json > scripts > install or package.json > scripts > postinstall. I'm wondering if you stumbled upon this error before, and how did you resolve it?

More info on my local setup:

➜ npm version
{ someproject: '1.0.0',
  npm: '6.4.1',
  ares: '1.15.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.15.3',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.51',
  zlib: '1.2.11' }

➜ uname -a
Linux computername 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

➜ cargo -V
cargo 1.40.0 (bc8e4c8be 2019-11-22)