by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:31
    paschaldev commented #873
  • 09:30
    Romakita commented #873
  • 09:17
    paschaldev commented #873
  • 09:17
    paschaldev commented #873
  • 09:09
    Romakita commented #873
  • 09:09
    Romakita commented #873
  • 08:59
    paschaldev closed #873
  • 08:58
    paschaldev commented #873
  • 06:38
    Romakita closed #871
  • 06:38
    Romakita commented #873
  • 01:10
    paschaldev labeled #873
  • 01:10
    paschaldev assigned #873
  • 01:10
    paschaldev opened #873
  • Jul 08 14:08
    Romakita commented #872
  • Jul 08 13:46
    tiran1984 commented #872
  • Jul 08 11:11
    Romakita commented #872
  • Jul 08 11:09
    Romakita commented #872
  • Jul 08 11:08
    Romakita commented #872
  • Jul 08 11:07
    tiran1984 commented #872
  • Jul 08 11:05
    Romakita commented #872
crimelabs786
@crimelabs786
A complete tutorial to a real app with CRUD kind of setup
Think TodoMVC app's backend
Romain Lenzotti
@Romakita
T.T another task I have to do
But I agree, it could be a good improvment for the new developper
crimelabs786
@crimelabs786
Yes
coding is the easy part :-D
adoption is up to how easy it is to get started
React won't be where it is today, without create-react-app
Romain Lenzotti
@Romakita
This the reason we have the @tsed/cli ^^
crimelabs786
@crimelabs786

This the reason we have the @tsed/cli ^^

:)

Yes, the CLI is a good idea
Is it on roadmap, to get to something similar to Rails CLI or Django CLI?
That'd be great
Being able to scaffold a new schema, or establishing a repl connection to DB
Romain Lenzotti
@Romakita
Issue added TypedProject/tsed#851
crimelabs786
@crimelabs786
If you're interested, I could take that up. Again, I'm not a backend person, in that I do work on backend from time to time, but my day job is front-end work.
We should discuss how we would structure this, and what all we should cover, as well as what we should NOT cover.
Romain Lenzotti
@Romakita
Is it on roadmap, to get to something similar to Rails CLI or Django CLI?
What do you mean?
Being able to scaffold a new schema, or establishing a repl connection to DB
This part is the responsability of TypeORM. But @tsed/cli has typeorm plugin to generate new connection (file). But to establishing real connection DB, is possibly out of the scope (currently) for Ts.ED project
Yes your help is welcome ;)
I have a react project example here https://github.com/TypedProject/tsed-example-react
It’s possible to start from this example and build the tutorial.

We should discuss how we would structure this, and what all we should cover, as well as what we should NOT cover.

sure :)

I think the maximum as it’s possible but we certainly with a small tutorials and add more things after ^^. I’m aware
Romain Lenzotti
@Romakita
@crimelabs786 DM me when you a time ;)
crimelabs786
@crimelabs786
@Romakita will do :)
Roberto Pesando
@psicomante

Ts.Ed looks like the next big thing in this world

i totally agree!

Romain Lenzotti
@Romakita
hooo so an online meetup in english should be a good idea
T.T my bad, I have to prepare that and improve my english skill
crimelabs786
@crimelabs786
@Romakita it's alright if your English is not up to par. English is just another language. If you're good in one language, that should be good enough for you to communicate your ideas, and then translators can translate that.
Romain Lenzotti
@Romakita
It’s should be fine with a good preperation
crimelabs786
@crimelabs786
Yes :+1:
Stefan van Herwijnen
@stefanvanherwijnen
@Romakita I am now getting this error ✖ Generate TypeORM configuration → Missing helper: "forEach" (node:107920) UnhandledPromiseRejectionWarning: Error: Missing helper: "forEach"
Probably caused by this change: https://github.com/TypedProject/tsed-cli/commit/ccb9253e544f110cec97138884b3c417fca08e5f#diff-9d9c4f489f9460d704806d7aeb0bd9a4
Let me know if I have to open an issue (my thought is not to open an issue for every trivial bug, but let me know if that is easier for you)
Romain Lenzotti
@Romakita
Strange, I fixed the cli because the helpers hadn’t correctly configured
Update the cli @tsed/cli and update also your @tsed/cli-plugin-* in your package.json
Stefan van Herwijnen
@stefanvanherwijnen
I did:
➜  typescript-jsonapi tsed --version
1.16.10
➜  typescript-jsonapi tsed init .
? Check the features needed for your project Database, File uploading with Multer, Swagger, Testing, Linter
? Choose a ORM manager TypeORM
? Which TypeORM you want to install? Postgres
? Choose unit framework Jest
? Choose linter tools framework EsLint
? Choose extra linter tools Prettier
  ✔ Install plugins
  ✔ Load plugins
  ✔ Install plugins dependencies
  ✔ Generate project files
  ✔ Generate files for eslint
  ✔ Generate files for jest
  ✔ Generate TypeORM connection file
  ✖ Generate TypeORM configuration
    → Missing helper: "forEach"
    Generate docker-compose configuration
    Install dependencies
    Run eslint
(node:109606) UnhandledPromiseRejectionWarning: Error: Missing helper: "forEach"
Romain Lenzotti
@Romakita
I haven’t this problem when I use the cli
Stefan van Herwijnen
@stefanvanherwijnen
Hmm, strange
Romain Lenzotti
@Romakita
Generated from scratch
? Check the features needed for your project Database, Testing, Linter
? Choose a ORM manager TypeORM
? Which TypeORM you want to install? Postgres
? Choose unit framework Jest
? Choose linter tools framework EsLint
? Choose extra linter tools Prettier
  ✔ Install plugins
  ✔ Load plugins
  ✔ Install plugins dependencies
  ✔ Generate project files
  ✔ Generate files for eslint
  ✔ Generate files for jest
  ✔ Generate TypeORM connection file
  ✔ Generate TypeORM configuration
  ✔ Generate docker-compose configuration
  ✔ Install dependencies
  ✔ Run eslint
➜  tsed-test tsed --version
1.16.10
"@tsed/cli-plugin-eslint": "1.16.10",
"@tsed/cli-plugin-jest": "1.16.10",
"@tsed/cli-plugin-typeorm": "1.16.10",
Stefan van Herwijnen
@stefanvanherwijnen
I'll try to reinstall the CLI, guess the plugins aren't updated. Thanks
Romain Lenzotti
@Romakita
Try from scratch and then in you project
Stefan van Herwijnen
@stefanvanherwijnen
The project dir is empty so it was from scratch. The problem was mixing up npm and yarn :sweat_smile: . I deleted the yarn install, updated the NPM one and now it works :thumbsup: . Which probably means that the CLI does not like yarn, but that seems to be a common problem with CLI's.
Romain Lenzotti
@Romakita
haaa ok :)
Hum no isn’t releated to the CLI. Yarn doesn’t install your packages in the same directory
(in global mode)
Stefan van Herwijnen
@stefanvanherwijnen
Makes sense, but that means the CLI does not work with yarn. Not something the CLI can solve, but it still is a problem for a global install. But the documentation says to use npm, so it really is my fault :grimacing: . Another CLI I have used (Quasar) specifically stated earlier to use npm instead of yarn, so I guessed it was just an intrinsic problem with yarn.
Romain Lenzotti
@Romakita
But there is no instruction in the cli code which is related to yarn directory location or npm directory location
Stefan van Herwijnen
@stefanvanherwijnen
Hmm, I tried it on a clean system install with yarn and it works fine. Must be something wrong on my system then, but good to know that yarn works fine :smile: . :thumbsup:
Romain Lenzotti
@Romakita
XD
Romain Lenzotti
@Romakita
Hello Guys
the first meetup was a great experience. I’ll try to work on its english version and prepare an online event :)
If you have some expected points about the framework or one of the its feature. Tell me :)
See you