René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"unable to resolve dependency tree","articleBody":"Hi I tried to run npx create-sourcebit with the options: contentful, transform-assets, and next and get the following error:\r\n\r\nError: Command failed: npm install sourcebit sourcebit-source-contentful sourcebit-transform-assets sourcebit-target-next --save\r\nnpm ERR! code ERESOLVE\r\nnpm ERR! ERESOLVE unable to resolve dependency tree\r\nnpm ERR! \r\nnpm ERR! While resolving: blog3@0.1.0\r\nnpm ERR! Found: next@10.1.3\r\nnpm ERR! node_modules/next\r\nnpm ERR!   next@\"10.1.3\" from the root project\r\nnpm ERR! \r\nnpm ERR! Could not resolve dependency:\r\nnpm ERR! peer next@\"^9.3.0\" from sourcebit-target-next@0.5.2\r\nnpm ERR! node_modules/sourcebit-target-next\r\nnpm ERR!   sourcebit-target-next@\"*\" from the root project\r\nnpm ERR! \r\nnpm ERR! Fix the upstream dependency conflict, or retry\r\nnpm ERR! this command with --force, or --legacy-peer-deps\r\nnpm ERR! to accept an incorrect (and potentially broken) dependency resolution.\r\nnpm ERR! \r\nnpm ERR! See /Users/andrewnjoo/.npm/eresolve-report.txt for a full report.\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR!     /Users/andrewnjoo/.npm/_logs/2021-04-15T16_01_31_041Z-debug.log\r\n\r\n    at ChildProcess.exithandler (child_process.js:308:12)\r\n    at ChildProcess.emit (events.js:315:20)\r\n    at maybeClose (internal/child_process.js:1048:16)\r\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) {\r\n  killed: false,\r\n  code: 1,\r\n  signal: null,\r\n  cmd: 'npm install sourcebit sourcebit-source-contentful sourcebit-transform-assets sourcebit-target-next --save'\r\n}\r\n(node:21239) UnhandledPromiseRejectionWarning: TypeError: Cannot destructure property 'errors' of '(intermediate value)' as it is undefined.\r\n    at /Users/andrewnjoo/.npm/_npx/dd234b8c5ef95e98/node_modules/create-sourcebit/index.js:23:13\r\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\r\n(Use `node --trace-warnings ...` to show where the warning was created)\r\n(node:21239) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)\r\n(node:21239) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.","author":{"url":"https://github.com/adnjoo","@type":"Person","name":"adnjoo"},"datePublished":"2021-04-15T16:04:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/20/sourcebit/issues/20"}