Bump package versions

[jorgebodega]

Currently some packages are outdated. We could update manually or try to update with some kind of bot, like renovate or dependabot.

This is the list

• @semantic-release/git
• Bump glob version #171
• Bump jest version #172
• Bump @types/node version #167
• Bump yargs version #173
• Bump eslint version #168
• Bump prettier version #166
• semantic-release
• Bump sqlite3 version #177
• Bump typeorm version #193
• Bump typescript version #164
• Bump chalk version #175
• Bump ora version #179

[jorgebodega]

I'm pretty sure we should discuss about what node version we support. This is pretty important, since Node 16 is going to be LTS this month, and because target are pretty diferent.

Node 12 tsconfig recommended
Node 14 tsconfig recommended
Node 16 tsconfig recommended

@hirsch88

[Dmitriyx]

we also need to upgrade faker dependency

yarn check v1.22.10 error "typeorm-seeding#faker" is wrong version: expected "4.1.0", got "5.5.3" error "nps#spawn-command-with-kill#ps-tree#event-stream" is wrong version: expected "=3.3.4", got "4.0.1" error Found 2 errors.

[jorgebodega]

faker is already upgraded on v1.6.2 but is not deployed because we do not have permission to do it. Check #156

[micalevisk]

will [email protected] be published soon? I want to use faker v5

$ npm info typeorm-seeding version
1.6.1

[jorgebodega]

New version cannot be released because of #153.

There is a workaround installing faker as a dependency and using it like

import * as faker from 'faker' // Use this instead of the other one
import { define } from 'typeorm-seeding'
import { User } from '../entities'

define(User, () => { ... })

[micalevisk]

oh of course. I felt dumb. Thanks

[jorgebodega]

I know that is not the ideal workaround.

If NPM token is not created when the next version will be ready, I will deploy it myself.

[jorgebodega]

Closing this, no versions could be deployed