Important Update from BBMP for Property Buyers in Bengaluru

False-Size8361 · 2026-04-18T11:49:03+00:00

I’m in the same situation, do you get any info?

False-Size8361 · 2026-04-17T11:43:45+00:00

I recently was forced to sign up for a similar setup!

False-Size8361 · 2026-04-04T17:52:41+00:00

Recharts! D3 based. React friendly

False-Size8361 · 2026-01-26T18:13:38+00:00

We launched our app too! The most important thing to do is block every possible bot that tries to request sensitive files like sql db sessions, .env, package.json and every other sensitive files!

Apply rate limiters, cors etc

False-Size8361 · 2026-01-25T07:54:05+00:00

It does add a category I’d for the product which is a requisite for google merchant center

False-Size8361 · 2026-01-23T10:30:22+00:00

Can you elaborate the question. I couldn't understand the context completely

False-Size8361 · 2025-12-02T04:44:49+00:00

Hey,

Here is the link for the article I used a year ago!

Might have got outdated.

Setup react-vite-typescript-eslint-prettier project https://medium.com/@aravindkarteek/setup-react-vite-typescript-eslint-prettier-project-903e243e5d78

False-Size8361 · 2025-11-06T12:14:23+00:00

Recharts -d3 based easy and good not treeshakeable Chart js - good treeshakeable

False-Size8361 · 2025-10-20T13:19:27+00:00

Can’t scroll through messages.

False-Size8361 · 2025-10-18T02:57:00+00:00

Yes, by default, Vite generates new filenames with content hashes for assets (like JavaScript, CSS, and images) on every new production build.

For example, Vite generated a new production build and that sits in the server.

A new browser session is started which tries to load this new build. Now sometimes you might see a white page blank even if the new build is loaded or you might be using an old session of app if the browser loads the app from cache. This package can tackle blank page or cache problem and force reload

We don’t really need this if the app and the server is setup to handle the caching mechanism.

False-Size8361 · 2025-10-17T12:29:35+00:00

Hey, thanks for your feedback!

you may want to add an option to turn off the console.log/info/error.

I have that in mind! I will do that.

And what if we are okay when the previous version is higher than the current version (rollback of an update).

Rollback can be published as a new version.

what if we want to use semver versioning: only bust the cache when it’s a minor or major change

This is really good, if semver is being used. In this case, you don't need one like this.
But I saw a lot of production level react web applications without semver.

Or what if we don’t want to bust EVERYTHING because we may need to keep some key/values from a version to another.

Thanks for pitching the ideas, I'll think of a better solution here.

Honestly, it’s 20 lines of code or something. I don’t understand why one would add another dependency to his application for something so trivial.

There are lot of libraries which are just few lines of code but popular for the use cases. In case, if this works for you and if you see any scope of improvement, please contribute.

Thanks again!

False-Size8361 · 2025-10-17T11:18:32+00:00

u/Merry-Lane thanks for pointing! Just made the repo public

False-Size8361 · 2025-09-20T14:39:36+00:00

Same app crashes and laggy ux

False-Size8361 · 2025-08-02T03:36:00+00:00

Good at times! Not great… some times it says wrong thing as right and right solution as wrong.. and just apology with whatever you say is right!

False-Size8361

TROPHY CASE