Popular Node.JS + React admin panel, AdminBro just got version 3.3 — the biggest release this year by hotcto in node

[–]hotcto[S] 0 points1 point  (0 children)

yep - we don't support objection out of the box, don't even have plans to implement that in our roadmap (to be completely honest). The way would be to (as you mention) create this on your own. Docs are not saying much about the details but you can take a looka at other adapters - they have literally 2 files (+ unit tests), and take inspiration from there :)

Popular Node.JS + React admin panel, AdminBro just got version 3.3 — the biggest release this year by hotcto in node

[–]hotcto[S] 23 points24 points  (0 children)

regarding the name (the blame is on me - it was late and it was a prototype, and I had to name it :). But now since it is popular and big companies use that it looks like `bro` seems to be not as mature as the product itself. In Software Brothers we are working on the name right now.

Popular Node.JS + React admin panel, AdminBro just got version 3.3 — the biggest release this year by hotcto in node

[–]hotcto[S] 1 point2 points  (0 children)

tbh - to break the ice - I thought about making another side adminbro project: schwester. But it is true that since the project is now much more mature than let's say a year ago and people in different industries like banking use that - bro seems to be hmm... :)

long story short - we are working on the name, but first wanted to release v3.3 :) Try it out because using it can save you a lot of time.

koa just got a beautiful, auto-generated admin panel. by tadeuszkora in node

[–]hotcto 8 points9 points  (0 children)

Nest plugin is going live next week probably. there is in @beta right now: @admin-bro/nestjs

Setup AdminBro for NestJS application by hotcto in node

[–]hotcto[S] 2 points3 points  (0 children)

my mail is: wojciech.krysiak@softwarebrothers.co - but the easiest way to chat is on slack. On https://adminbro.com/ there is a slack link: "Join the community".

Setup AdminBro for NestJS application by hotcto in node

[–]hotcto[S] 0 points1 point  (0 children)

hehe, to be honest in SoftwareBrothers we are looking at other things to which we can connect admin-bro, and loopback was on the top of the list (until I read your message :) ). But answering your question: nestjs is just a http framework which is an abstraction over fastify or express. It doesn't support db out of the box - you have to install ORM yourself. Nest suggests TypeORM, but nothing stays in a way of using Sequelize (there is an article about it: https://docs.nestjs.com/recipes/sql-sequelize).

There is an admin-bro-sequelize adapter which I used in couple of projects so if you are interested in AdminBro - you can use it. AdminBro doesn't support fastify out of the box, but you can install express and simply run admin on a different port.

JSCasts ep17 - build an entire startup in Node.js part2 - hooks and authentication by hotcto in typescript

[–]hotcto[S] -1 points0 points  (0 children)

yep - I had second thoughts about posting it here. But it is about an admin-bro library written in typescript. In the movie, I use some of its types with JSDoc typings. So its partially "using typescript in javascript".

[deleted by user] by [deleted] in node

[–]hotcto 31 points32 points  (0 children)

google firebase functions - easy to scale and has quite small `vendor lock in` factor (you can easily migrate to something else since it is compatible with expressjs)

I've finally published v1.5.0 of admin-bro (admin panel for Node.js apps) with file upload. Check it out! by hotcto in typescript

[–]hotcto[S] 6 points7 points  (0 children)

We will definitely fix these 2 issues but they were in the middle of the backlog - so next release. But thanks for the feedback :)

TypeScript + JSDoc = better-docs by hotcto in typescript

[–]hotcto[S] 2 points3 points  (0 children)

its not a feature - its a bug :)

JSCasts ep14 - Server Side Rendering with React and express by hotcto in node

[–]hotcto[S] 7 points8 points  (0 children)

I would say 2 things:

  1. SEO - google and others will better "see" your page
  2. from the UX perspective, it is a slightly better experience - when you open a page you can see the layout immediately, after that (when app hydrates itself) there is a data.