Hello everyone, newbie here, if you could answer some of the question I have for my react app to be

[mighty peak]

converted into next.

I am intermediate in react, I have been learning next since 2 hours and I am really enjoying it so far. I was working on a project for a client(mid size website) using react express postgre sql, and I think we would benefit using next for some part of the site for SEO. here are my question:

So far I have found limited resources for working with postgres in nextjs, all of them requires prisma, I found an article that has used postgres without prisma, so it is possible to use right? no problems?
Article: https://www.simplenextjs.com/posts/next-postgresql

So, since, I used redux in application, I can work around it in nextjs as well, thats awesome.

this might seem stupid but I wanted to ask all the npm packages that works in react also works in nextjs right? I only have one significant package i must use, I hope it works, i will try soon after.

lastly, I had this question. So, my application is like this: homepage, but when I go to location, like timeout.com, timeout.com/sydney , timeout.com/melbourne , those location page are same but its content is different. in next i will have folder structure: pages/[id].js ? likewise, those location have their own products, like timeout.com/sydney/product-1 , so, structure will be pages/sydney/[id].js ?

thank you!

[runic sky]

Hey,

I also just started with next and love it. so 2 newbies here.

For your question, pages/sydney/[id].js is correct.

[mighty peak]

thanks

[mighty peak]

<Link href='/'>
  <a><Logo src="https://www.timeout.com/static/images/logo.png" /></a>
</Link>

guys above code is giving me errors. I added the images: {
domains: ['localhost', 'www.timeout.com']
} in the config
still not working
I also tried <Image width height>

Its fixed

[runic sky]

Did you only added them to next.config.js or also another place?

I have a similar issue when loading images with cloudinary

[mighty peak]

only on the config. my issue was the incorrect import of Link. instead of { Link }, its import Link from 'next/link'