Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project not correctly initialized according to documentation #2916

Closed
2 tasks done
ketzu opened this issue Nov 19, 2023 · 1 comment · Fixed by #2899
Closed
2 tasks done

Project not correctly initialized according to documentation #2916

ketzu opened this issue Nov 19, 2023 · 1 comment · Fixed by #2899
Labels
regression A bug, but worse scope: toolpad-studio Abbreviated to "studio"

Comments

@ketzu
Copy link

ketzu commented Nov 19, 2023

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Steps to reproduce 🕹

Steps:

  1. npx create-toolpad-app@latest xyz
  2. cd xyz
  3. npm run dev

Current behavior 😯

C:\dev\toolpadtest> npx create-toolpad-app@latest xyz

info - Creating Toolpad project in C:\dev\toolpadtest\xyz

info - Initializing package.json file
info - Initializing .gitignore file
info - Installing dependencies

npm WARN deprecated [email protected]: The original `String.prototype.at` proposal has been replaced by a new one; please use v1 or later of `string.prototype.at` instead

added 806 packages, and audited 807 packages in 2m

177 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

success - Dependencies installed successfully!

Run the following to get started:

  cd xyz
  npm run dev

C:\dev\toolpadtest> cd .\xyz\
C:\dev\toolpadtest\xyz> npm run dev

> [email protected] dev
> toolpad dev

info  - starting Toolpad application in dev mode...
(node:22684) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
error - No project found at "C:\dev\toolpadtest\xyz\toolpad". Use the --create option to initialize a new Toolpad project in this folder.

Expected behavior 🤔

A correctly initialized folder that works as described in the documentation.

Context 🔦

Initialize a new project to give toolpad a try.

Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 11 10.0.22621
  Binaries:
    Node: 21.2.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Chromium (119.0.2151.72)

No browser was used in this experiment. Although usually I'd use firefox (which seems undetected).

@ketzu ketzu added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Nov 19, 2023
@Janpot
Copy link
Member

Janpot commented Nov 19, 2023

will be fixed by #2899

@Janpot Janpot added regression A bug, but worse and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Nov 20, 2023
@oliviertassinari oliviertassinari added the scope: toolpad-studio Abbreviated to "studio" label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression A bug, but worse scope: toolpad-studio Abbreviated to "studio"
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants