Skip to content

Renaming js to ts requires server restart #1336

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

Closed
rsmith-cs-ux opened this issue Sep 28, 2020 · 2 comments
Closed

Renaming js to ts requires server restart #1336

rsmith-cs-ux opened this issue Sep 28, 2020 · 2 comments
Labels
build Ideas for or bugs with the build process

Comments

@rsmith-cs-ux
Copy link

Hi there!

While running ember s, whenever I generate a new component everything works just fine and the changes are automatically detected. But when I rename the file from .js to .ts (because I'm using typescript) I have to restart the server because the changes break everything. It would be great if it could detect the change and handle it properly. I filed the issue with ember-cli and they said it sounded like an issue with ember-cli-typescript (ember-cli/ember-cli#9345).

Thanks!

User story

As a user, I want to rename files from .js to .ts without having to restart the ember server.

@chriskrycho chriskrycho added the build Ideas for or bugs with the build process label Oct 15, 2020
@chriskrycho
Copy link
Member

I believe this is related to #724, and should be a function of the ember-cli-babel build, not anything ember-cli-typescript does anymore, assuming you're on a sufficiently recent version of both ember-cli-babel and ember-cli-typescript: does this reproduce on latest of both? If so, it's actually a fundamental limitation in the way the build pipeline works. If not, I'm very curious what the issue would be.

cc. @rwjblue

@chriskrycho
Copy link
Member

We now recommend that people switch to using ember-cli-babel for apps (as documented here) and the rollup plugin configured as part of the v2 add-on build for add-ons, in conjunction with running glint or tsc directly on their projects. Accordingly, although this should not be an issue, even if it is we will not be addressing it, as we are moving this package into maintenance mode. Thanks!

@chriskrycho chriskrycho closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Ideas for or bugs with the build process
Projects
None yet
Development

No branches or pull requests

2 participants