Feedback on roadmap to AdonisJS 7

[RomainLanz]

👋 Hey everyone,

We just published the roadmap for AdonisJS 7! It includes a ton of exciting features: a new Lucid ORM release, type-safe routing, better Inertia support, built-in notification system, updated encryption layer, and much more.

This is our vision for the next major release, and while some parts are still evolving, we'd love to get your feedback early.

✅ v7 tasks dashboard: AdonisJS 7 Tasks
👉 Read the full article here: https://adonisjs.com/blog/roadmap-to-adonisjs-7
💬 Let us know what you think in the comments: what you're excited about, what concerns you, and what you'd like to see next!

Thanks for being part of the community 🙌

[stctheproducer]

The encryption update, Tanstack query integration and notifications system are the features I'm most excited to see. This is a solid roadmap! 🎉

[batosai]

For my part, very interested in the notification system and HTTP transformer. Can’t wait to see the new lucid but also some fear for the adaptation of my package (adonis-attachment ><)

Adonis queue will also be for v7?

[thetutlage]

The attachment package will be still usable

[RomainLanz]

Adonis queue will also be for v7?

Maybe before!

[nfadili]

Hi! Major kudos to the AdonisJS team for sharing such a thoughtful roadmap to begin with! I am incredibly grateful for how much care and effort you all put into keeping AdonisJS stable while still moving the framework forward. Your excellent documentation and articles like this one are a huge help for that.

Very very excited about the announcements for Transformers, autogen types/URLs, and improvements to Tuyau. We are currently operating a fairly large monorepo with multiple AdonisJS services and various frontend/backend apps that need to call them and one of our biggest painpoints is maintaining the types and clients for calling them. It'd be great to have more tooling available to maintain typesafe clients and used them in the monorepo as well as outside it.

[henriquealbert]

Awesome work, folks! 👏🏻
Really liked Lucid being standalone, notifications, and the types features
Do you already have a release date in mind?

[RomainLanz]

No date in mind yet!

[MatteoGauthier]

I like the fact that Adonis is more and more part of the React ecosystem (Tuyau + TanStack Query, jsx examples, utils for frontend)

[RomainLanz]

We're not shifting toward React specifically, we just want to provide good DX helpers regardless of your frontend stack.

[jakubkoje]

As someone not using react, thank you for not locking into a single ecosystem. Currently using Tuyau with Nuxt 3 and integration with tanstack query regardless of the framework would be awesome.

[Julien-R44]

Tuyau will also have an integration for @tanstack/vue-query

But, for others frameworks like Svelte, Angular, or Solid, to be honest I’m not sure. Community contributions would be welcome, but I don’t see myself building adapters for every framework

[lncitador]

it's very nice to see the constant evolution of adonisjs, reading this part of the article makes me realize that what I imagine as something beneficial for the ecosystem, the maintainers also align themselves with. when I read this part of the article you posted https://adonisjs.com/blog/roadmap-to-adonisjs-7#http-transformer, it reminded me of a gist that I created for personal use in my projects https://gist.github.com/lncitador/2fd9650a9e7872f631404e2b1a721ed0 which is very raw but which I eagerly await the official implementation

[ThisIsMissEm]

I like the encryption changes, one thing that I would like to be able to do is mark an environment variable as sensitive (i.e., making the result a Secret that needs to be released to be used, as to avoid accident logging of the environment variables).

Notifications is interesting, but has a lot of project-dependent needs, e.g., does it support grouped notifications or debouncing?

I would like to see a better flash notification system for more common CRUD style success / warning / error type flash notifications, since these are super common in CRUD applications, but currently need to be manually implemented in every app.

I'd also like to see database query logging in development, ala rails, the request on discord has screenshots.

And I'd also love to see URL builder support absolute URL generation by using a PUBLIC_URL environment variable — in many of my apps I need to generate fully qualified URLs, and have a built-in for that would be nice. Currently just use .prefix() doesn't work as it can end up with double slashes in URLs.

It'd also be neat to be able to do a rescue_from at a controller level for various errors, before passing up to the exception handler.

[ThisIsMissEm]

rescue_from is a rails thing, I'm not sure if it's best practice or not. This article shows it pretty well: https://dev.to/rossonevan/generate-more-detailed-errors-in-controllers-using-rescuefrom-in-ruby-on-rails-12i0 — docs: https://guides.rubyonrails.org/action_controller_advanced_topics.html#handling-errors

Controller hooks are also really powerful (before_action, after_action and around_action), especially when you do inheritance. https://guides.rubyonrails.org/action_controller_overview.html#controller-callbacks

Could you open a GitHub issue for this?

absolutely, where would you like it? Core?

[ThisIsMissEm]

Also, really happy to hear about logging by default for requests. Currently I have a code snippet I copy around projects for exactly this.

[JanStevens]

Some additional notes on the debug logging.

In rails there are 2 different type of logs at the START and the END of a request.
At the Start of a request all submitted params / searchParams are logged followed by the database requests and finally how long it all took, example (straight from the docs). Note how they differentiate between "render time" vs "database record time"

Started POST "/articles" for 127.0.0.1 at 2018-10-18 20:09:23 -0400
Processing by ArticlesController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"XLveDrKzF1SwaiNRPTaMtkrsTzedtebPPkmxEFIU0ordLjICSnXsSNfrdMa4ccyBjuGwnnEiQhEoMN6H1Gtz3A==", "article"=>{"title"=>"Debugging Rails", "body"=>"I'm learning how to print in logs.", "published"=>"0"}, "commit"=>"Create Article"}
New article: {"id"=>nil, "title"=>"Debugging Rails", "body"=>"I'm learning how to print in logs.", "published"=>false, "created_at"=>nil, "updated_at"=>nil}
Article should be valid: true
   (0.0ms)  begin transaction
  ↳ app/controllers/articles_controller.rb:31
  Article Create (0.5ms)  INSERT INTO "articles" ("title", "body", "published", "created_at", "updated_at") VALUES (?, ?, ?, ?, ?)  [["title", "Debugging Rails"], ["body", "I'm learning how to print in logs."], ["published", 0], ["created_at", "2018-10-19 00:09:23.216549"], ["updated_at", "2018-10-19 00:09:23.216549"]]
  ↳ app/controllers/articles_controller.rb:31
   (2.3ms)  commit transaction
  ↳ app/controllers/articles_controller.rb:31
The article was saved and now the user is going to be redirected...
Redirected to http://localhost:3000/articles/1
Completed 302 Found in 4ms (ActiveRecord: 0.8ms)

As a rails developer this kinda of logging is super handy! And missing in adonis. Another big win about this type of request logging is that you get very good insights in "what kind of DB queries am I doing and does this even make sense"

[RomainLanz]

That's unlikely to be doable in the same way, since our HTTP server handles multiple requests concurrently, making it hard to maintain a per-request context for logging like Rails does.

That said, this could become feasible with the diagnostic channel support coming in the next version.

[ThisIsMissEm]

In development, you could collect the logs for a given request and dump them all at once once the request ends (e.g., via using diagnostics channel)

But even if the requests are interleaved it's better than nothing — I can show you this on the FIRES project, where I have this enabled and it's super handy in development.

[iamtommcc]

Super exciting! Transformers in particular look amazing, I'd be keen to see what the full API ends up being.

Although I am curious... to the incoming first-class support for queues/jobs? I recall this being tweeted about several months ago.

Whilst there are some decent third party packages out there (e.g. adonis-resque), queues to me are a foundational element to any serious backend project and are becoming increasingly critical in the world of AI agents. Vercel mentioned that they were their most requested feature, and there's even been an entire microindustry of SaaS offerings spin up due the fact that many frameworks don't have first class queue support (Trigger.dev, Inngest).

Admittedly queues can be quite the slippery slope scope-wise - especially for observability - but even ability to dispatch lightweight database-driven queue jobs in core would be lovely.

EDIT: I just saw above that queues is still coming - amazing news and sounds like I'm preaching to the choir already 😆

[magnus-trent]

Absolutely excited for standalone Lucid! I've been waiting for so long 😭

[FroDK]

I've been using Adonis for about a year, and I really like it. I haven't encountered any major issues or bottlenecks, but I would like to see built-in support for generating openapi schema and swagger. This is something that's really missing

[magnus-trent]

https://friendsofadonis.com/docs/openapi which wraps https://openapi-ts.dev/ is a great solution to this.

[kitro]

As a professional Laravel developer trying AdonisJs for the couple last months, It was a good experience so far, the features includes in v7 roadmap will sharp the framework. one thing I miss is the builtin queueing system, like Laravel queue/horizon and soft delete in models, model binding in routes.
But overall AdonisJs looks promising.

[iamtommcc]

@RomainLanz @thetutlage A few more coherent thoughts on transformers, having implemented this pattern in some absolutely massive Laravel applications

• There's overlap with things like Tuyau and OpenAPI spec generation as you highlighted
  • In some of the larger scale Laravel apps our transformers evolved more into "describers" and also end up handling things like field labelling for doc generation etc. I wonder if some of this docgen/describer functionality– or at the very least, the metadata to enable it – is best incorporated into core.
• It's tempting to think of Transformers as being tied/coupled 1:1 to a model but this can pose some limitations IMO (especially when considering endpoints that aren't directly CRUD related). You mentioned in the docs that models aren't required (which is good!); it'd be interesting to see what this story ends up looking like, or what it looks like when multiple models are involved.
• Other things that might be relevant:
  • Case changing utils when picking from models directly
  • Extra serialisation helpers for certain data types
  • "Includes"/sparse field sets (dynamic property inclusion/relation resolving)
  • Pagination

[paulo-steinberg]

As someone coming from Laravel, I also really miss the queue package. It would be amazing if v7 had it built in.

[bdavidxyz]

Coming from Rails, I badly miss a buit-in queue system, along with the dashboard (solid_queue/ mission_control).

[arnauddoub]

It would be great if request validation supported Zod, so we could share the same validators between the backend and the frontend.

[thetutlage]

Yes, we will be making the request.validateUsing method https://standardschema.dev/ complaint. Also, I will later look into making Vine work on the frontend as well.

[EwertonDutra]

Hi, it's great to see the framework's evolution. I used version 5 a lot.

I even presented it to a lot of people here in Brazil, and it's usually a pleasant surprise.

Can anyone tell me if database validations are back?

At the beginning of version 6, I noticed that validations like unique email addresses directly in the database and other similar validations involving the database were no longer available :(

[ifullgaz]

Hi, I'm not entirely sure if that's what you mean:
https://docs.adonisjs.com/guides/basics/validation
There is more in the VineJS documentation, including a way to implement a unique rule:
https://vinejs.dev/docs/extend/custom_rules
I hope that helps

[RomainLanz]

I noticed that validations like unique email addresses directly in the database and other similar validations involving the database were no longer available :(

They haven't been removed. Validations that rely on the database (like checking for unique email addresses) are still available and are provided by Lucid as extensions to Vine. You can find the documentation here: https://lucid.adonisjs.com/docs/validation

[EwertonDutra]

I noticed that validations like unique email addresses directly in the database and other similar validations involving the database were no longer available :(

They haven't been removed. Validations that rely on the database (like checking for unique email addresses) are still available and are provided by Lucid as extensions to Vine. You can find the documentation here: https://lucid.adonisjs.com/docs/validation

Cool,
That's right @RomainLanz.

I looked it up and it was released at the end of 2024, right?
https://github.com/adonisjs/lucid/releases/tag/v21.5.0

And tutorial in jan 2025
https://adocasts.com/series/adonisjs-quick-tip/lessons/new-unique-and-exist-validation-overloads-in-adonisjs-6

At the beginning of version 6, it wasn't there. It was a pain to have to do these manual validations (there were projects that were in version 5), and the people who had seen it in version 5 also really missed it. Since it was there, removing it was a bad thing.

But I'm glad it's back 🎉👏, I'll share it here with everyone.

[EwertonDutra]

Hi, I'm not entirely sure if that's what you mean: https://docs.adonisjs.com/guides/basics/validation There is more in the VineJS documentation, including a way to implement a unique rule: https://vinejs.dev/docs/extend/custom_rules I hope that helps

Thanks @ifullgaz

[JanStevens]

Hi,

Another feature for inertia would be using streamable responses so we can use renderToPipeableStream instead of renderToString when using SSR.

See https://react.dev/reference/react-dom/server/renderToPipeableStream

Regards,

[holoyan]

Hi,

Any chance we can have a polymorphic relationship support?

If not it would be great if you document how relations can be customized, I'll try to create a lib