-
Notifications
You must be signed in to change notification settings - Fork 136
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
Choose js vs jsx #24
Comments
Hello @DavidSSchwartz I had the same problem, just fixed this in a fork of mine in case you're interested. npm i -D github:fsgreco/new-component Then use Repo: https://github.com/fsgreco/new-component This fork also has a sightly benefit that you can now give the name you want it will always convert it in PascalCase. (unfortunately I changed things and made a pull request before known that this project is not under active maintenance. So nowadays I just use my fork for new projects) |
Maybe its a lack of documentation, but according to sources you can issue Also it is possible to create config file to make this setting persistent, like: {
"lang": "jsx"
} |
As of now new-component doesn't provide any way to create components of but I recently forked this library and made some changes to achieve this: if you have previously installed this library globally / at project level, uninstall it.
now you can add components traditionally as Side Note |
I'm working with Vite and it seems to not allow jsx in js files. I'd be happy to add, maybe an '-x' flag to create files as jsx.
I see an earlier version had something similar to this. Wondering if your open to putting something similar to what was (but more focused) back in.
The text was updated successfully, but these errors were encountered: