Skip to content

npx create-tsrouter-app@latest gives ERROR #221

Closed

Description

@flyingduck92

Which project does this relate to?

Create Tanstack App

Describe the bug

npm error code ECOMPROMISED
npm error Lock compromised

Your Example Website or App

Steps to Reproduce the Bug or Issue

  1. npx create-tsrouter-app@latest

  2. Need to install the following packages:
    create-tsrouter-app@0.34.15
    Ok to proceed? y

  3. npm error code ECOMPROMISED
    npm error Lock compromised
    npm error A complete log of this run can be found in: C:\Users\sekti\AppData\Local\npm-cache_logs\2025-11-01T09_43_06_580Z-debug-0.log

Expected behavior

Image

After npx command will choose:

  1. File-based or code-based route configuration
  2. TypeScript support
  3. Tailwind CSS integration
  4. Toolchain setup
  5. Git initialization

Screenshots or Videos

Image

Log file :
2025-11-01T09_51_40_753Z-debug-0.log.txt

Platform

  • OS: Windows 10

Additional context

No response

Activity

  1. jherr commented on Nov 1, 2025

    @jherr
    Collaborator

    Not seeing this on OSX. Perhaps this is a Windows specific issue? Have you tried running this in WSL 2?

  2. flyingduck92 commented on Nov 2, 2025

    @flyingduck92
    Author

    @jherr WIndows issue? do you mean the cause are coming from nvm? I already reinstall the node and nvm but the issue the same. No, i have not tried using WSL 2.

  3. jherr commented on Nov 2, 2025

    @jherr
    Collaborator

    I don't mean nvm. I mean, running node on Windows outside of WSL 2 is known to have issues. So since you are seeing something that we don't see on other OS'es, perhaps it's the OS. In which case I recommend going with WSL 2. It's the easiest fix for node issues on Windows.

  4. flyingduck92 commented on Nov 2, 2025

    @flyingduck92
    Author

    @jherr I see, I decided to change the package manager to pnpm since the npm not working in my end for tanstack-router.

  5. jherr commented on Nov 2, 2025

    @jherr
    Collaborator

    And it worked?

  6. flyingduck92 commented on Nov 2, 2025

    @flyingduck92
    Author

    @jherr its working with pnpm

    Image Image
  7. flyingduck92 commented on Nov 3, 2025

    @flyingduck92
    Author

    @jherr apparently this issue coming from npm-cli itself -> npm/cli#8710

  8. jherr commented on Nov 3, 2025

    @jherr
    Collaborator
  9. flyingduck92 commented on Nov 4, 2025

    @flyingduck92
    Author

    @jherr you're most welcome sir

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions