Mark Salsbery

@matiasgarcia I'm curious what your "typeorm" script looks like in your package.json...if you posted it, I'm not seeing it sorry ;)

> > @matiasgarcia I'm curious what your "typeorm" script looks like in your package.json...if you posted it, I'm not seeing it sorry ;) > > I tried everything: > >...

Thanks to @pleerock and [this post](https://github.com/typeorm/typeorm/issues/8814#issuecomment-1080945772) I now have migration creation/generation working. The CLI now requires the full path to the output file, so if you have an npm script...

> I also got the migrations to work but only by compiling my code and using .js data-source file. I still can't get the migrations to work using the .ts...

@SleeveShirtholes here's my relevant package.json stuff... typeorm version is different than yours I noticed... ```json { "dependencies": { "mssql": "^8.0.2", "reflect-metadata": "^0.1.13", "typeorm": "^0.3.4" }, "devDependencies": { "@types/node": "^17.0.23", "@types/tedious":...

@SleeveShirtholes are you sure all dependencies are updated to latest versions and installed? That looks like it's not seeing ts-node

@SleeveShirtholes hmm, I got nothin ;) If you added the typeorm script to package.json and that script runs typeorm-ts-node-esm then the only difference from what I'm doing is I'm not...

> Yes, you have to use `dotenv` or `@nestjs/config` witch is using dotenv internally. > > OK, i had some other issue, some of the commands don't work, for example...

@myflowpl I reread and noticed it was only the create that didn’t use -d and realized that operation wouldn’t need the database so that’s why it works. Sorry for the...

@berkaygurbuz As @iangilman mentioned, OSD viewers keep their own state. Just like most, if not all, React state handling, it's just going to be problematic (and unnecessary) to save state...