Skip to content

Error: @inquirer/type does not provide 'CancelablePromise' when running npm create amplify@latest #2015

@Julianrvillamil

Description

@Julianrvillamil

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v20.17.0

Amplify CLI Version

12.12.6

What operating system are you using?

Windows (WSL)

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

I'm encountering an issue when trying to run the command npm create amplify@latest. The error I receive is:

import { CancelablePromise } from '@inquirer/type';
         ^^^^^^^^^^^^^^^^^
SyntaxError: The requested module '@inquirer/type' does not provide an export named 'CancelablePromise'

This error occurs after updating Node.js to version 20.17.0 and reinstalling all dependencies. The issue seems to be related to the Amplify CLI depending on an incompatible version of the @inquirer/type package.

I also tried installing both @inquirer/core and @inquirer/type manually, but the error persists.

Expected behavior

When I run the command npm create amplify@latest, I expect the process to proceed without errors. Specifically, the Amplify CLI should guide me through the setup process for configuring a new Amplify project or adding a backend to my existing frontend application. This should include prompts for setting up authentication, API, storage, or other Amplify services, without encountering issues related to the @inquirer/type or CancelablePromise.

Reproduction steps

  1. create a new nextJS project
  2. run npm create amplify@latest

Project Identifier

Learn more at https://docs.amplify.aws/cli/reference/diagnose/
⠋ Creating Zip
No Amplify backend project files detected within this folder.
✖ Creating Zip

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependencyIssue related to upstream dependencypending-triageIncoming issues that need categorization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions