On registry https://registry.npmjs.org/, the "latest" version (v3.2.1) of dependency nsp has the following deprecation notice:

The Node Security Platform service is shutting down 9/30 - https://blog.npmjs.org/post/175511531085/the-node-security-platform-service-is-shutting

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.

Please take the actions necessary to rename or substitute this deprecated package and commit to your base branch. If you wish to ignore this deprecation warning and continue using nsp as-is, please add it to your ignoreDeps array in Renovate config before closing this issue, otherwise another issue will be recreated the next time Renovate runs.

The exporting to a serverless folder fails with the following error:

Error: Cannot export when target is not server. https://err.sh/zeit/next.js/next-export-serverless
    at _default (/home/ubuntu/server/jspsych_Big5/node_modules/next/dist/export/index.js:1:3018)
    at nextExport (/home/ubuntu/server/jspsych_Big5/node_modules/next/dist/cli/next-export.js:20:325)
    at commands.(anonymous function).then.exec (/home/ubuntu/server/jspsych_Big5/node_modules/next/dist/bin/next:29:346)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
    at Function.Module.runMain (module.js:695:11)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3

I'm using the latest npm on Ubuntu 16.04.

Please check https://ipip.ori.org/newMultipleconstructs.htm and see if it is possible to modularize b5-web such that they can allow other inventories to work.
As a base example please add https://ipip.ori.org/30FacetNEO-PI-RItems_Maples_etal.htm to the system, which is published in 2014 along Johnson's inventory.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

This issue contains a list of Renovate updates and their statuses.

Open

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

• Update dependency jcb64 to v4

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