Skip to content

🐛 [Bug report]: *js/*ts files are not being generated upon creation of a play #775

Closed as not planned

Description

@bhaveek424

Descrcibe the bug?

After running the command npx create-react-play -c <my unique play code>, only a directory is created and it doesn't contain any files. I've tried it by selecting both javascript and typescript at the time of add a play, but none seems to generate their respective files.

Steps to reproduce the bug?

  1. After selecting the play and getting the npx .... command, run the npx ... command
  2. It will create a directory/folder with the same name of the project
  3. The folder won't have any files.
  4. It will be an empty folder.

Expected behavior

It is expected to create a file named DrawingBoard.js if selected Javascript.

Desktop (Please provide your system information)

OS: Ubuntu(Linux)
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
Browser: Firefox, Brave

Mobile (Please provide your device information)

No response

Screenshot / Screenshare

react-play-bug2
react-play-bug1

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. atapas commented on Oct 31, 2022

    @atapas
    Member

    The same is reproducible on Mac too.

  2. koustov commented on Dec 3, 2022

    @koustov
    Member

    This issue has been fixed as part this pr. I need a confirmation if its working in order to close this issue.

  3. github-actions commented on Jan 2, 2023

    @github-actions

    There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

  4. reopened this on Sep 7, 2023
  5. github-actions commented on Oct 16, 2023

    @github-actions

    There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingnmn-22No Mess November 2022stale

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions