Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
npm production migrate?
See original GitHub issueI have run with an issue recently when pushing code to production. commands/ormconfig.ts has src/env hardcoded instead of src/dist. This presents a “problem” when doing migrations with the built code, would you mind if I add a new command in package.json?
P.S Awesome work in the package!
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
migrate - npm
Start using migrate in your project by running `npm i migrate`. There are 70 other projects in the npm registry using migrate.
Read more >migrations - npm
Start using migrations in your project by running `npm i migrations`. There are no other projects in the npm registry using migrations.
Read more >db-migrate - npm
Start using db-migrate in your project by running `npm i db-migrate`. There are 159 other projects in the npm registry using db-migrate.
Read more >node-pg-migrate - npm
Postgresql database migration management tool for node.js. Latest version: 6.2.2, last published: 6 months ago. Start using node-pg-migrate ...
Read more >node-db-migration - npm
Source control for your database. This is the dummies and simplest package that allows you to automatically install new migrations on your ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@et could you have a look at https://github.com/w3tecch/express-typescript-boilerplate/pull/95 and provide some feedback what you think. Thanks
@dweber019 - what would help though for people though is to provide uniformity with the db env variables. So in the .env file, they should be renamed to
TYPEORM_variables.