When on typescript project, sequelize-cli still generates javascript files.

Open
#1,436 12 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
cli

Research direction

Start by running the reported sequelize init and migration CLI commands in a TypeScript project and inspect the generated migration, seed, and model files. Done means these generated files use the .ts extension and are compatible with the project; the payload names no implementation files or tests.

Written by the indexing model from the issue text.

Description

What I am doing?

I'm using Sequelize-cli in a typescript project and it is not generating .ts files and I have to then update those files extensions and make manual changes to the file for making it compatible in my project.

What I expect to happen?

I want to have the CLI work the same for my typescript file as it does for a javascript project. I expect the cli to generate proper migration, see and model files with .ts extension.

What is actually happening?

When I try to run sequelize init or other migration cli, it will generate javascript files instead of typescript as expected.

Dialect: mysql
Database version: latest
Sequelize CLI version: latest
Sequelize version: latest

Would you resolve this issue by submitting a Pull Request?

  • Yes, I have the time and I know how to start.

I have completed and fully tested the configuration and changes needed for this issue fix, but I am not able to push my work into the repository. Could you please help me get access so that I can push my work on this issue?

Dominant language
JavaScript
Stars
2.6k
Forks
524
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/cli

All issues in sequelize/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.