How To Set Up Next.js 15 For Production In 2025

Поділитися
Вставка
  • Опубліковано 29 січ 2025

КОМЕНТАРІ • 49

  • @eliuddyn
    @eliuddyn 8 днів тому +1

    Amazing 🔥🔥

    • @JanHesters
      @JanHesters  8 днів тому

      Thank you!
      What would you like to see next?

  • @MrBumbo90
    @MrBumbo90 2 місяці тому +3

    Instant favorites list channel. You summarized a lot of what I have been pondering as I moved from simple apps that have a couple of pages to working on a complex project with a team.

    • @JanHesters
      @JanHesters  2 місяці тому

      Thank you for the kind words! 🙏

  • @Myhic-lt4xy
    @Myhic-lt4xy 3 місяці тому +5

    This is a rare channel, and I love the atmosphere your in.

    • @JanHesters
      @JanHesters  2 місяці тому +1

      Appreciate it!
      I like shooting outside because we are inside enough as developers haha

  • @Next-Js
    @Next-Js Місяць тому +3

    You are very good at explaining, the content is interesting.

  • @hbela1000
    @hbela1000 2 місяці тому +1

    I am happy to come across this exelent tutorial.Instant subscription of course.

  • @ManosFregkos
    @ManosFregkos Місяць тому +1

    Accidentally i faced up on the article that describes that video, when i saw the authors name, you went me back 4 years in EarlyNode when i meet you first time ( for a few days ) Jan! You are amazing tutor Jan, you have a lot of good stuff to learn to developers, you have earned a loyal subscriber!!

    • @JanHesters
      @JanHesters  Місяць тому +1

      Thank you for the kind words! 🙏

  • @markschneidermann
    @markschneidermann 3 місяці тому +3

    dope style & crazy gold nuggets bro !

    • @JanHesters
      @JanHesters  2 місяці тому

      I have the privilege of working with the best when it comes to style 😉 Thanks!

  • @josippardon8933
    @josippardon8933 2 місяці тому +1

    1) I like the video, subscribed
    2) you give vibe that you just dropped new crypto trading course which will make me a millionare in just 3 months
    3) 0:33 what is this thing running in background?!???

    • @JanHesters
      @JanHesters  21 день тому

      1.) Thank you!
      2.) Never selling trading courses lol But I might make videos on how the blockchain works in the future because it might become more relevant.
      3.) Haha some other people in the park during that day.

  • @Pushpaje2130
    @Pushpaje2130 2 місяці тому +3

    Amazing video ❤

  • @Deus-lo-Vuilt
    @Deus-lo-Vuilt Місяць тому +2

    I would like to see a video of this complete where each thing can be explained in more detail :3

    • @JanHesters
      @JanHesters  Місяць тому

      Got it. I'm def planning on dedicated videos for each of these technologies.
      Thank you for sharing your feedback! 🙏

  • @ZeeshanMukhtar-e7y
    @ZeeshanMukhtar-e7y Місяць тому +1

    Love from Pakistan

    • @JanHesters
      @JanHesters  21 день тому

      Love back from Germany! x3

  • @naimurrahman9979
    @naimurrahman9979 2 місяці тому +1

    This video is gold and your energy is unmatched, you earned a loyal subscriber, hoping to get gold contents coming on... 🔥🔥

    • @JanHesters
      @JanHesters  2 місяці тому +1

      Thank you for the kind words! More to come 🔥
      And just curious, anything specific you'd like to see?

    • @naimurrahman9979
      @naimurrahman9979 2 місяці тому

      @@JanHesters If you're on to SaaS, you can share how we can research for SaaS, market and scale. Recently I was trying to build a SaaS project but stuck at some point to find the unique solution I was looking for, for example: do stuffs by pdf selection such as highlight, translate, take notes, explanation via ai, and then get them together in a docs.

  • @dreamsachiever212
    @dreamsachiever212 3 місяці тому +2

    You gotta love YT algorithm. Spent 3 days setting up a monorepo using turborepo, hell of a pain... Could you create a similar video on setting up for production for a monorepo?

    • @JanHesters
      @JanHesters  2 місяці тому +2

      Absolutely! But it will take a few months, I have a bunch of other topics planned first.
      Thank you for the compliment and the suggestion! 🙏

  • @alvierime
    @alvierime 2 місяці тому +3

    Internationalization needs a dedicated tutorial

  • @Rajesh-rg6fw
    @Rajesh-rg6fw Місяць тому +1

    This really good video. As I know next.js is very difficult to host it in any other platform other than vercel, and vercel is too expensive. and if the app is too big or backend heavy application then in that case also you thing next.js is the best choice as full stack, or only in frontend or react, and a separate backend?

    • @JanHesters
      @JanHesters  Місяць тому

      Thank you for your comment! 🙏
      There are tons of alternatives like AWS, DigitalOcean, or Railway. When using Remix, I also often work with Fly.io.
      In my opinion, Next.js can handle full-stack development with its API routes easily. I'd only break out your backend for complex or special needs. Then separating the backend (e.g., using Node.js, Go, Django, or others) can be a better approach.

  • @mehmethanifierenler3612
    @mehmethanifierenler3612 3 місяці тому +1

    very very thanks

  • @chad_giga6934
    @chad_giga6934 2 місяці тому +4

    Programming Andrew Tate, lol no hate here bro.
    I just find your approach interesting, something that is not common in this space

    • @JanHesters
      @JanHesters  2 місяці тому

      Thank you! I wanted to try something new haha! 🙏

  • @mattymattffs
    @mattymattffs 3 місяці тому +2

    Question, are the terrible shirts a requirement too?

    • @JanHesters
      @JanHesters  2 місяці тому +2

      Right into the feels! 💔😄 Wear whatever you want 😉

  • @peepoclown5838
    @peepoclown5838 2 місяці тому +4

    This video gave me a headache...

    • @JanHesters
      @JanHesters  2 місяці тому

      Why? 😄

    • @tobydixonsmith6126
      @tobydixonsmith6126 Місяць тому

      @@JanHesters My guess is because you’re talking really quickly. I get not wanting to be too slow, but people who like to go through content at a quicker pace (such as myself) can set their playback speed quicker. So your normal pace should be slow enough for people to comfortably understand what you’re talking about. But great video other than that minor nit pick

    • @JanHesters
      @JanHesters  Місяць тому

      @@tobydixonsmith6126 Thank you for the feedback! 🙏 I'm experimenting with my deliver style in upcoming videos.

    • @gobifrontend
      @gobifrontend Місяць тому

      ​@@JanHesters to be honest it's really fast and loud for me. Btw nice content ❤.

  • @jamescbender43081
    @jamescbender43081 2 місяці тому +1

    I hate Husky, and we don't allow it in our shop. It just creates more friction, and you can do everything Husky does as part of your pipeline when someone sends a PR.

    • @devyb-cc
      @devyb-cc 2 місяці тому

      i use webstorm, i see no reason to use husky 😅

    • @jamescbender43081
      @jamescbender43081 2 місяці тому +1

      @@devyb-cc I've never used WebStorm, so I don't know how they compare, but I HATE the idea of Git pre-commit hooks in general.

    • @devyb-cc
      @devyb-cc 2 місяці тому

      @@jamescbender43081 well, jetbrains products all have something like hook. i usually do it only to analyze my code, in case i left some TODOs or unused imports.

    • @JanHesters
      @JanHesters  2 місяці тому

      Interesting!
      How do you do it? Do you just run linting and type checks in CI/CD and let people push even with linting or type errors?

    • @jamescbender43081
      @jamescbender43081 2 місяці тому

      @@JanHesters Yeah, we let developers send PRs up with linting errors. Before anyone even reviews it, it will run through the CI/CD pipeline, so linting, and all tests (unit, E2E, etc.) get run automatically and have to pass before the PR can be approved, no matter how many votes it gets. We do this for a few reasons. First, I want all the long-running/resource-intensive steps to run on the server so they can run faster without blocking the developer from working on something else. This also ensures that the branch will integrate with the existing branch. The other big reason, and why we stay away from pre-commit hooks (like Husky) is that I want my developers to be able to commit (locally) frequenty, even if these commits are "work in process" commits, aka "I want to commit what I have so that if the next thing I try to do totally f's things up, I can go back to the last commit." and making them conform to a bunch of rules designed to protect the main branch causes a lot of friction, and discourages these kinds of commits. As log as the "last" commit that's part of the PR conforms to the rules, as enforced by the pipeline, I don't care what the previous commits in that PR do.