Seb Van Sande

Hi. I'm trying to understand the added value of your feature request. So I have a few questions for you: 1. Why are you updating a migration file? 2. What...

Are you suggesting the same as [#141](https://github.com/seppevs/migrate-mongo/issues/141)?

You can also just remove the migration files each time you do a big release (and all migrations are applied in all environments)? If you have put your migrate-mongo project...

Did you try to setup your own `package.json` in your migrate-mongo project directory, and add a logging library (eg. winston) as a dependency? If so, you could configure your own...

Closing this.

See last comment for a workaround. Issue is not directly caused by migrate-mongo, so I'm closing this.

Closing this. Issue is not caused by migrate-mongo IMHO.

Merged and landed in v11.0.0. Sorry for the delay. Thank you for your contribution.

Merged and landed in v11.0.0. Sorry for the delay. Thank you for your contribution.

Closing this, see last comment for resolution.