adrianhajdin / projects_realestate

Build and Deploy a Real Estate React & Next.js Application

Real Estate App

🌟 Become a top 1% Next.js 13 developer in only one course

🚀 Land your dream programming job in 6 months

projects_realestate's Issues

Error: Missing "key" prop for element in iterator react/jsx-key

Hydration error

Hydration failed because the initial UI does not match what was rendered on the server

Current next version 11.1.2 has a high security issue

Current next version 11.1.2 has a high security issue:
next: 11.1.2 Known security vulnerability: 1 Security advisory: 0 Highest severity: high

Error

I get the error below whenever I start up the server after updating the next.config.js file so as to parse the image. Please can you help me

API not connecting

Api somehow is not connecting and getting timed out

Application Error

there's some error when we click on a property card on home page , also no link in menu working,
Kindly look into it.

PS : I'm a fan your work, respect and peace.

Investing in Excellence: The M3M Paragon Advantage

Elevate your investment portfolio with the M3M Paragon Advantage. This article explores how M3M Paragon stands as a beacon of excellence in real estate investment. From its strategic location to the unparalleled quality of construction, discover why M3M Paragon is not just a property but a promise of enduring value. Investing in excellence has never been more enticing than with the M3M Paragon Advantage.

'ERR_HTTP_INVALID_HEADER_VALUE',

after running the npm run dev i get the event-compiled successfully then the server generates a new error"'ERR_HTTP_INVALID_HEADER_VALUE',"

TypeError: propertyForRent.map is not a function can anyone solve this error

Fix to work with latest versions of NodeJS

I started with latest version of Node.js v18.17.1 and hit this issue:

❯ sudo npm run dev

> [email protected] dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
node:internal/crypto/hash:69
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at BulkUpdateDecorator.hashFactory (/Users/j/ResilioSync/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:138971:18)
    at BulkUpdateDecorator.digest (/Users/j/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:138906:21)
    at getHash (/Users/j/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:101615:45)
    at getLongModuleName (/Users/j/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:101695:25)
    at /Users/j/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:102180:24
    at assignNames (/Users/j/ResilioSync/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:101894:22)
    at /Users/j/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:102173:28
    at Hook.eval [as call] (eval at create (/Users/j/ResilioSync/github.com/adrianhajdin/projects_realestate/node_modules/next/dist/compiled/webpack/bundle5.js:33818:10), <anonymous>:7:1) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.17.1

To fix this I either had to downlevel NodeJS to v16. OR run legacy SSL as suggested here:

https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported

This project ought to be fixed to work with the latest version of NodeJS.

Application Client Side Error

Browser hangs

After working around issue #18 , I tried running the app:

❯ npm run dev

> [email protected] dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
event - compiled successfully
event - build page: /
wait  - compiling...
event - compiled successfully
event - build page: /next/dist/pages/_error
wait  - compiling...
event - compiled successfully
event - build page: /next/dist/pages/_error
wait  - compiling...
event - compiled successfully
wait  - compiling...
event - compiled successfully

When directing my browser to localhost:3000, it just hangs. There's nothing showing up the terminal. The browser's console shows nothing, but eventually shows this:

crbug/1173575, non-JS module files deprecated.
(anonymous) @ VM46:5

Any ideas?

Api Not connecting

Unveiling Elegance: M3M Antalya Hills Residences

Step into a world of timeless elegance and refined living at M3M Antalya Hills. Located in the heart of Antalya, Turkey, this exclusive residential development sets the standard for luxury living. With breathtaking views and unparalleled amenities, every detail is thoughtfully designed to exceed expectations. From spacious interiors to lush green surroundings, immerse yourself in the epitome of sophistication. Discover a sanctuary where tranquility meets indulgence, where every moment is a celebration of opulence. Welcome to M3M Antalya Hills, where luxury knows no bounds and dreams come to life.

Reference Error

router is not defined in SearchFilters.jsx

Alhaithaminvestments

100% profit guaranteed Real estate development ideas.
#- [x] Earn increase upto 30% in your new/existing business ~~~~~~~~

Error

Hey!! After installing code file in my local desktop and all dependencies, whenever I try to build production by typing the command next build
I am facing this error Cannot find module 'next/dist/shared/lib/is-plain-object.js'

Could someone help me with this?

TypeError: filters.map is not a function

please help me to solve this error

AxiosError: Request failed with status code 403

thanks Ms adrian for you wonderful videos it very helpful>

I am facing issue with Axios I tried to fix it but I couldnot.
may you drop a comment for solution to proceed in project practicing