![Anthony Shew](/img/default-banner.jpg)
- Видео 5
- Просмотров 28 810
Anthony Shew
Добавлен 28 ноя 2011
Played pro ⚾ for 6 yrs. Now I’m a full-stack comedian. Currently @vercel.
Turborepo 2.0 - New UI + Watch Mode?!
Turborepo 2.0 improves the developer experience of JavaScript and TypeScript repositories, with features including:
→ New terminal UI: Interactive tasks and clearer logs
→ Watch Mode: Dependency-aware task watcher for any tooling in your repository
→ All-new documentation: Core monorepo concepts, refreshed API reference, and ecosystem tooling guides
Go check it out!: turbo.build/blog/turbo-2-0
Twitter: anthonysheww
Discord: discord.gg/JMHERJGRkH
Everything else: shew.dev
→ New terminal UI: Interactive tasks and clearer logs
→ Watch Mode: Dependency-aware task watcher for any tooling in your repository
→ All-new documentation: Core monorepo concepts, refreshed API reference, and ecosystem tooling guides
Go check it out!: turbo.build/blog/turbo-2-0
Twitter: anthonysheww
Discord: discord.gg/JMHERJGRkH
Everything else: shew.dev
Просмотров: 5 690
Видео
Do less, ship more (in a monorepo)
Просмотров 814Месяц назад
Just because there's more code in your monorepo doesn't mean it has to be slower. Ship faster by doing less in a Turborepo. Learn about Turborepo: turbo.build Twitter: anthonysheww Discord: discord.gg/JMHERJGRkH Everything else: shew.dev 0:00 Our shared monorepo experience 0:46 Monorepos vs. polyrepos 2:02 Making a monorepo fast locally 5:07 Using ` filter` 6:00 Global `turbo` 8:08 ...
Node.js runs on Turborepo now
Просмотров 3,5 тыс.2 месяца назад
Turborepo can help you ship single-package workspaces, too, just like a monorepo. Let's take a look at how the Node.js team is doing it. Node.js repository: github.com/nodejs/nodejs.org/tree/50eb2ee348aaa48d0817b017afcfb6a17f896300 Twitter: anthonysheww Discord: discord.gg/JMHERJGRkH Everything else: shew.dev
Internationalization with the Next.js 13 App Router
Просмотров 18 тыс.Год назад
Learn how to set up basic internationalization in the Next.js App Router! GitHub example: github.com/anthonyshew/i18n-demo Twitter: anthonysheww Discord: discord.gg/JMHERJGRkH Portfolio: shew.dev
Migrate to the Next.js App Router with confidence (and feature flags)
Просмотров 872Год назад
Using Vercel's Edge Config can help you transition into the Next.js App Router from the Pages Router using zero latency feature flags. You can ship the App Router with confidence, knowing that you can rollback to your existing views from `/pages` in seconds. GitHub example: github.com/anthonyshew/edge-config-migration-demo Twitter: anthonysheww
Thank you for the good work
Decent, keep going
I had some problem to install tailwind in the UI folder, can you give me some documentation for that? I can't find it
The new terminal ui is horrible, you can't copy and paste anything from it
Thank you very much for the video... could you make an example connecting the prism orm with the new version of turborepo?
Try out `npx create-turbo@latest -e with-prisma`. More examples can be found here: turbo.build/repo/docs/getting-started/installation#start-with-an-example
@@anthonyshewww Thanks my friend... yes... the repository I have checked... and I have tried to do it several times.... but unfortunately I have NOT been able to connect yet..... I don't know what I am doing wrong... that's why I'm interested in seeing a practical example.... again thank you for answering..... hopefully you can make an example, maybe more people will be interested in it.
Cool ui!
what is this browser?
Arc!
Please share your neovim config 🫣
My dotfiles are here!: github.com/anthonyshew/dotfiles (Although, it’s not updated. I’ll push an update soon.) 🙃
Its on my list to try out turborepo, some cool features there!
This looks like an awesome tool
how does one get your setup
My dotfiles are here!: github.com/anthonyshew/dotfiles
Thanks for the video. Sorry for the abuse could you use a series of turborepo from basic to advanced level ... sweia super master turborepo greetings from Venezuela your new subscriber Jose Grillo NOTE; do you have a discord channel?
Awesome content thank you!! Anyone wondering the terminal UI seems differernt from yours, set "experimentalUI" to true in your turbo.json!
nice video, subscribed cause of nvim!
Great content, subscribed :D
Cool, I have to finally learn neovim
It took me ~5 tries and then I used www.lazyvim.org/ I still have a ton to learn but feel a lot faster already.
Neovim is absolutely amazing!
Kinda clickbait in title :/
Yup. Node.js does NOT run on Turborepo, their official website does. It's a shame the author felt the need to clickbait audience this way because the content of the video was actually good. I won't be subscribing to the channel for that reason.
@@Lars16 true that
very cool stuff, you should make videos more often
I appreciate that! Definitely going to be doing more. 👍
Look at you neovimming everywhere like a pro
It's so good. I have so much to learn.
Turborepo is super cooolllll !
no u
Great stuff! it simply works and love that I don't need to change the actual path in the user's browser. A nice follow up would be to show how one could give the user a language switcher and override this preferred lang parameter at the browser level, for instance saving the override in a cookie. The part that would be challenging is adapting this middleware to do that.
What about Date Time translation?
if this didn't work and you have a src folder don't forget to put you middleware file in your src file not in root
Hey Anthony! great video, in Next 14 docs they don't show how to change language
awesome! can you tell me how to toggle/switch between different locales from frontend?
how can you merge with the nextAuth middleware?
Ask how can I make a button that changes the language between Spanish and English, good video, it helped me a lot
Hi Mr. Anthony, Your tutorial on using Next.js for a multi-language website has been a real lifesaver for me. I've learned a lot about using next-intl for fixed content, but I've run into a challenge with dynamic content like user-created posts and comments. I'm not sure how to add them to the locales JSON files, and I've had trouble finding helpful resources on this topic. I would be really grateful if you could point me in the right direction and maybe even consider creating a tutorial on handling dynamic content within the locales JSON files. Your help would mean a lot to me and others facing similar challenges. Thank you so much,
how can i show locale in the url
hahahahaha un poco español, awesome tutorial Anthony!
Hello, I have a question why I set the default language but it doesn't work?
Thank you for the video.. but is that a good practice for SEO or its better each language in a separate route as /sp ??
Hah, nice. RUclips recommended this video right after I made the same thing.
Could you do a video explaining how to make the internationalization and private routes in the middleware? Because it's hard to configure both. Thanks
in the middleware file I had to change the ```export const config = { matcher: [ '/((?!_next|api|favicon.ico).*)', ] }``` for ```export const config = { matcher: ['/((?!api|_next|.*\\..*).*)'] };``` since the images in the public folder were not working. Everything else worked just fine 😊
this is great! i was looking for. is there a any document to improve my matcher knowledge?
Absolute life saver, thanks for that!
any solution for SSG + App Router + i18n. since middleware not supported in static export mode
Thanks for sharing! Spent quite a lot of time to configure i18n in my project and get some ideas from your video. Just have one more question: how would you organize singular/plural keys inside of dictionary in this type of keys getting? :) And also how would you separate this dictionary files in case of much bigger amout of keys?
thank you very much for your video, everything works perfectly except for not-found.tsx at the root of [lang] I can't get the params
Curious to ask, is the i18n conversion of this approach server side or client side ?
the cleanest i18n solution. thanks. more tutorials please.
I logged only to like, subscribe and comment this video, great! thx a lot for this! 😀👍
What about switching between the languages with a dropdown menu? how to handle that ?
i think you can use this import { useRouter } from 'next/router' const router = useRouter() const { pathname, asPath, query } = router // change just the locale and maintain all other route information including href's query router.push({ pathname, query }, asPath, { locale: nextLocale })
hello can you add example if im on home page : i consume only home stings,same for other pages like load translation per page only
What would happen if you actually had the lang in the url? Would it rewrite to /en/en/some-path?
sobre yo better put Acerca de mi, 😊😊
Hi , i have a question , i want a button that change my local from /fr to /en , i could not do it , i tried to use usestate etc , but nothing happend
same here i made a dirty solution to change it, considering default lang is english location.replace(pathname.includes("es")? "/en" + pathname.slice(3) : "/es" + pathname)
@@alexqs96 i'll try it , thank u
@@alexqs96 Hi again , i have a server component , how can get this pathname
@@nourrahim5556 the button that i used was a client component using usePathname, then imported that button component into my server component
BIG NOTICE: To get params in layout we need to put it inside [lang] folder. If it lays outside of the [lang] (as shown in the video), the language in html won't change and you woldn't be able to pass it to the layout components such as header and footer. Now everything seems to work) Thanks for the video, it's trully the best way to impement internalization
Oh gosh, major oops! I might have to re-record. BIG YES! Pinning.
it works fine for me...
Yes Header and Footer Components require this, had an issue with the ../globals.css import but once I re-ran it was all ok. Great tutorial :)
Do you have an example pls
Thanks mate! I subscribed Twice, ready to support you ❤️
How would you avoid creating a massive dictionary will all the translations ? I imagine this will not be efficient for client side components
You pretty much have to create a massive dictionary if you want a lot of content. There are tools like Lokalise to manage that, but it’s not free.
Nice crisp video on I18n 👏 One observation though, the Root Layout does not receive params, hence lang attribute remains "en" as it is always defaultLocale. Any thoughts around it?
To get params in layout we need to put it inside [lang] folder. If it lays outside of the [lang] (as shown in the video), the language in html won't change and you woldn't be able to pass it to the layout components such as header and footer. Now everything seems to work)
You could add a custom header, like x-locale and use it in layout with headers().get(“x-locale”). Then you don’t even need the params property