DEV Community: Rishi Bhardwaj

I Built Tinder for Open Source Contributions 🔥

Rishi Bhardwaj — Fri, 17 Jul 2026 17:44:33 +0000

Finding your first open source contribution shouldn't feel like searching for a needle in a haystack.

Yet that's exactly what happens.

You open GitHub, search for good first issue, open dozens of repositories, scroll through outdated issues, read confusing descriptions, and eventually... close the tab.

There had to be a better way.

That's why I built IssueSwipe.

The Problem

Every year thousands of developers want to contribute to open source.

The motivation is there.

The repositories are there.

The issues are there.

But discovering the right issue for your skill level is surprisingly difficult.

Some common problems:

Too many repositories to explore
Issues that are already solved or inactive
Beginners don't know where to start
Switching between dozens of GitHub tabs
No personalized recommendations

Instead of writing code, you're spending time searching for code.

Meet IssueSwipe

Imagine Tinder...

But instead of people, you're discovering open source issues.

Swipe right if you want to contribute.

Swipe left if you're not interested.

Bookmark interesting issues for later.

That's the entire idea.

Simple.

Fast.

Fun.

What Makes It Different?

🃏 Swipe-Based Discovery

Instead of endless GitHub searching, every issue appears as a card.

One swipe is all it takes.

🧠 Smart Matching

IssueSwipe doesn't show random issues.

It recommends issues based on:

Programming languages
Interests
Experience level
Repository metadata
GitHub labels

The goal is simple:

Show developers issues they're actually likely to contribute to.

🏆 Gamification

Open source is rewarding.

It should also feel rewarding.

IssueSwipe includes:

XP System
Developer Ranks
Daily Streaks
Contribution Tracking

Every interaction moves your profile forward.

🔖 Save Issues

Found something interesting but don't have time?

Bookmark it.

Track its progress from:

Saved → Working → Pull Request → Merged

🔄 GitHub Integration

IssueSwipe synchronizes issues using the GitHub GraphQL API.

It focuses on labels like:

good first issue
help wanted

So you're always browsing contribution-friendly issues.

Tech Stack

Built with technologies I genuinely enjoy working with:

Next.js 16
TypeScript
Prisma
SQLite
Tailwind CSS v4
Framer Motion
GitHub OAuth
JWT Authentication

Why I Built It

Open source changed the way I learned development.

But getting started was never easy.

I wanted something that made discovering contributions feel less like searching documentation and more like exploring opportunities.

Something that beginners could enjoy.

Something experienced contributors could use every day.

IssueSwipe is my attempt to make open source more approachable while keeping the experience engaging.

What's Next?

Some features I'm planning include:

AI-powered issue recommendations
Team contribution mode
Repository recommendations
Achievement badges
Leaderboards
Advanced filters
Organization dashboards

Open Source

IssueSwipe is completely open source, and contributions are always welcome.

Whether you're fixing bugs, improving the UI, adding features, or suggesting ideas—I'd love to collaborate with you.

If you've ever wanted to contribute to open source, maybe your next pull request starts with a swipe.

Thanks for reading!

If you like the idea, I'd love to hear your thoughts, feature suggestions, or feedback in the comments.

Happy contributing. 🚀

From Curiosity to Community: Why I Started Omnikon

Rishi Bhardwaj — Fri, 17 Jul 2026 17:11:39 +0000

I'm a Computer Science student and the founder of Omnikon, an open-source organization built around one idea: students learn the most by building real projects with real people.

Like many developers, I started by following tutorials and building small projects. They taught me the basics, but I realized they couldn't replicate the experience of collaborating with others, reviewing code, solving real problems, and maintaining software over time.

That's why I created Omnikon.

What is Omnikon?

Omnikon is an open-source community where developers can collaborate on meaningful projects, improve their technical skills, and contribute to software that others can actually use.

Our focus isn't just on writing code—it's about learning industry practices like:

Version control with Git and GitHub
Code reviews and collaboration
Writing maintainable software
Open-source contribution workflows
Building projects from idea to deployment

My Goal

I want Omnikon to become a place where students don't feel intimidated by open source.

Whether you're making your first pull request or leading a feature, every contribution matters. The goal is to create an environment where people can learn by doing and grow alongside other developers.

What You'll Find Here

On this blog, I'll be sharing:

My journey as a student developer
Lessons from building Omnikon
Open-source experiences
Project development insights
Tips for new contributors
Things I learn while exploring new technologies

I'm still learning every day, and that's exactly what makes this journey exciting.

If you're passionate about building, learning, and contributing to open source, I'd love to connect with you.

Let's build something meaningful together. 🚀

— Rishi Bhardwaj, Founder of Omnikon

Contribute to Omnikon in GSSoC 2026

Rishi Bhardwaj — Fri, 17 Jul 2026 17:09:52 +0000

🚀 Contribute to Omnikon in GSSoC 2026

Looking to make meaningful open-source contributions this GSSoC? We'd love to have you at Omnikon.

Our organization is focused on building practical tools and developer-focused projects where contributors can learn, collaborate, and make a real impact. Whether you're fixing bugs, improving documentation, designing UI, or implementing new features, there's a place for every skill level.

Why contribute to Omnikon?

💻 Work on real-world open-source projects
🌱 Learn modern development workflows
🤝 Collaborate with an active community
⭐ Build a stronger GitHub profile
📈 Gain valuable experience through meaningful contributions

If you're participating in GSSoC 2026 and want projects that help you grow as a developer, check out our repositories, explore the issues, and start contributing.

Happy coding, and see you in the pull requests! 🚀
https://github.com/Omnikon-Org/Astrodex/issues

opensource #gssoc #github #webdevelopment #javascript #typescript #developers #community

Our Journey to GSSoC 2026: Omnikon's Repository Has Been Selected! 🎉

Rishi Bhardwaj — Thu, 09 Jul 2026 21:08:37 +0000

Open source has always been at the heart of what we do at Omnikon. Today, we're excited to share a milestone that means a lot to our entire community.

Our repository, maintained by Sourabh, has been officially selected for GirlScript Summer of Code (GSSoC) 2026.

For us, this isn't just another achievement—it's a step toward building a stronger open-source ecosystem where students and developers can learn, collaborate, and create meaningful software together.

About Omnikon

Omnikon is a student-led open-source organization focused on building high-quality developer tools, educational resources, and community-driven projects. Our mission is simple:

Build impactful open-source software.
Help new contributors get started.
Create projects that solve real problems.
Foster a welcoming developer community.

Every repository we build is designed with collaboration in mind, making it easier for contributors of all experience levels to participate.

What GSSoC Means

GirlScript Summer of Code is one of India's largest open-source programs. Every year, thousands of contributors participate by solving issues, improving documentation, fixing bugs, and implementing new features across selected repositories.

Being selected means our project will become part of this collaborative ecosystem, giving contributors an opportunity to make meaningful contributions while learning industry-standard development workflows.

A Special Thanks

This achievement wouldn't have been possible without Sourabh, who maintained and prepared the repository throughout the selection process.

A huge thank you to everyone who contributed ideas, reviewed code, reported issues, improved documentation, and supported the project. Open source is never the work of one person—it grows because of a community.

What's Next?

We're preparing the repository for contributors by:

Organizing beginner-friendly issues.
Improving documentation.
Creating contribution guides.
Enhancing project structure.
Mentoring new contributors throughout GSSoC.

Whether you're making your first pull request or you're an experienced developer, there will be opportunities to contribute and learn.

Join Us

If you're participating in GSSoC 2026, we'd love to have you contribute to our repository. Explore the issues, ask questions, submit pull requests, and become part of the Omnikon community.

Every contribution—no matter how small—helps improve the project and strengthens the open-source ecosystem.

Thank You ❤️

This milestone marks the beginning of an exciting journey rather than the end of one. We look forward to collaborating with contributors from across the community, learning together, and building something impactful through GSSoC 2026.

See you in GSSoC, and happy contributing! 🚀

CNTRL by Omnikon Org Selected for Elite Coders Summer of Code (ECSoC) 2026

Rishi Bhardwaj — Sun, 05 Jul 2026 18:43:01 +0000

🚀 CNTRL by Omnikon Org Selected for Elite Coders Summer of Code (ECSoC) 2026

Building an AI-first browser for developers—and taking the next step through ECSoC 2026.

Open source has always been one of the best ways to learn, collaborate, and build software that makes a difference. Today, I'm excited to share a milestone that means a lot to our team.

Our project CNTRL, developed by Omnikon Org, has officially been selected for Elite Coders Summer of Code (ECSoC) 2026! 🎉

This selection gives us an incredible opportunity to collaborate with contributors worldwide and continue building a browser that's designed from the ground up for developers.

💡 Why We Started CNTRL

Every developer has experienced this workflow:

Open documentation
Search GitHub
Ask an AI assistant
Open Stack Overflow
Copy code
Switch back to the IDE
Repeat...

The browser has become the center of development, but it still isn't designed for developers.

We wanted to change that.

Instead of building another browser, we started building one where AI is part of the experience—not another tab.

🌐 What is CNTRL?

CNTRL is an AI-powered browser built for developers.

Our vision is to create a browser that understands how developers work and helps them stay focused.

Some of the ideas we're working toward include:

🤖 AI-assisted coding
📖 Context-aware documentation
💬 Built-in developer assistant
⚡ Faster research workflows
🔌 Extensible architecture
🌍 Community-driven open source

The project is still evolving, and ECSoC gives us the perfect platform to accelerate its development.

🏆 Selected for ECSoC 2026

Being selected for Elite Coders Summer of Code 2026 is a huge milestone for our organization.

It means we'll have the opportunity to:

Collaborate with talented contributors
Improve the project's architecture
Build exciting new features
Learn from the community
Grow CNTRL into an even better developer tool

We're incredibly thankful to the ECSoC team for believing in our vision.

🌍 About Omnikon Org

Omnikon Org is an open-source organization focused on creating modern developer tools while helping students and developers contribute to meaningful projects.

We believe that open source should be accessible, collaborative, and impactful.

CNTRL is one of the biggest steps toward that vision.

🤝 We'd Love Contributors

Whether you're a beginner or an experienced developer, we'd love to have you contribute.

We're looking for help in:

React
TypeScript
Tauri
Rust
AI & LLM Integrations
UI/UX Design
Documentation
Testing

Every contribution helps move the project forward.

🔗 Check Out CNTRL

⭐ GitHub Repository

https://github.com/Omnikon-Org/CNTRL

If you find the project interesting, consider:

⭐ Starring the repository
🐛 Opening issues
💡 Suggesting features
🔨 Submitting pull requests
📢 Sharing it with other developers

❤️ Looking Ahead

Getting selected for ECSoC is only the beginning.

Over the next few months, we'll continue building CNTRL in public, collaborating with contributors, sharing our progress, and working toward our vision of creating an AI-first browser for developers.

Thank you to everyone who has supported Omnikon Org so far.

We're excited for what's ahead.

Let's build something amazing together. 🚀

Connect with Us

🌐 GitHub: https://github.com/Omnikon-Org/CNTRL

⭐ If you like the project, don't forget to leave a star!

Happy Coding! ❤️

opensource #webdev #javascript #typescript #react #rust #tauri #ai #github #productivity #devtools #buildinpublic

🚀 How We Organized a Frontend Quiz That Attracted 1,600+ Registrations

Rishi Bhardwaj — Thu, 02 Jul 2026 19:31:06 +0000

Building software is exciting.

But building a community around technology? That's even more rewarding.

Recently, our team at Omnikon organized our very first large-scale community event—the Frontend Quiz Arena 2026.

We had no idea how many people would register.

Our initial goal was simple:

If a few hundred students participate and learn something new, we'll consider it a success.

Instead, the response completely exceeded our expectations.

By the end of registrations, we had crossed 1,600+ registrations from students across India.

Here's everything we learned from organizing our first tech event.

🎯 Why We Created the Quiz

When we started Omnikon, we didn't want to become "just another developer community."

Our vision was to create opportunities where students could:

Learn
Compete
Build confidence
Meet other developers

A frontend quiz felt like the perfect first step.

Instead of asking interview-style trick questions, we wanted participants to think like real frontend developers.

🛠️ Building the Quiz

Creating a quiz sounds easy.

In reality, it involved weeks of work.

We spent time:

Researching topics
Writing balanced questions
Reviewing every question multiple times
Testing difficulty
Preparing certificates
Planning announcements
Designing banners

The final quiz covered topics like:

HTML
CSS
JavaScript
React
Responsive Design
Accessibility
Browser APIs
Performance Optimization
Modern Frontend Practices

Our goal wasn't to make people fail.

Our goal was to help them learn.

📢 Promotion Was Everything

One thing we learned quickly:

A great event doesn't automatically get participants.

Promotion became just as important as creating the quiz.

We shared updates on:

LinkedIn
Discord
X (Twitter)
Reddit
College Communities
WhatsApp Groups

Instead of posting only registration links, we shared milestones, countdowns, updates, and interacted with participants throughout the event.

That consistency made a huge difference.

📈 The Result

The registrations kept growing every day.

Eventually, we crossed:

🚀 1,600+ registrations
🏫 Students from colleges across India
📜 Participation certificates
🏆 Cash prizes for winners
💬 Hundreds of community interactions

For our very first major event, this was an incredible milestone.

💡 Lessons We Learned

1. Start Before Everything Is Perfect

There were countless things we wanted to improve before launching.

If we had waited until everything felt perfect, we'd probably still be planning instead of organizing.

Launching taught us far more than planning ever could.

2. Community Is More Important Than Numbers

Yes, 1,600+ registrations felt amazing.

But the best part wasn't the number.

It was seeing participants discuss questions, invite friends, and return for future events.

That's when we realized we weren't just organizing quizzes—we were building a community.

3. Consistency Beats Virality

None of our posts went massively viral.

Instead, we showed up every day.

We answered questions.

We posted updates.

We celebrated milestones.

Small actions repeated consistently created a much bigger impact than waiting for one viral moment.

4. Every Event Is a Learning Experience

No event is perfect.

There were things we'd do differently next time.

But that's part of the process.

Every event helps us improve the next one.

🚀 What's Next?

The Frontend Quiz was only the beginning.

We're already organizing more events, including:

🤖 AI/ML Quiz Challenge
💻 Backend Quiz
🏆 Coding Competitions
🚀 Hackathons
🌍 Open Source Programs

Our mission remains the same:

Create opportunities that help students learn, build, compete, and grow.

❤️ Thank You

To everyone who participated, shared our posts, invited friends, or supported Omnikon—

Thank you.

This milestone wouldn't have been possible without the community.

We're excited for what's ahead, and we hope to see you in our future events.

Happy coding! 🚀

What was the first tech event you ever organized or participated in? I'd love to hear your experience in the comments. 👇

webdev #frontend #javascript #react #css #html #opensource #community #students #learning #devchallenge

I Was Tired of Downloading the Same npm Packages—So I Built PackVault

Rishi Bhardwaj — Mon, 29 Jun 2026 20:56:43 +0000

I Was Tired of Downloading the Same npm Packages—So I Built PackVault

Every JavaScript developer has done this countless times:

npm install

Wait...

Download React.

Download Vite.

Download TypeScript.

Download Tailwind CSS.

Repeat for every new project.

Eventually I started asking myself:

Why am I downloading the same packages over and over again?

That question eventually turned into PackVault.

The Problem

Modern JavaScript development assumes you always have internet access.

But that's not always true.

✈️ Working on a flight
🌐 Slow or unstable internet
🎓 Workshops with dozens of students
🔒 Air-gapped environments
💻 Setting up multiple development machines

Even if you've already downloaded a package before, you'll often end up downloading it again.

So I Built PackVault

PackVault is an offline-first package caching CLI for JavaScript developers.

Instead of repeatedly downloading dependencies, PackVault lets you cache them once and reuse them whenever you need them.

# Cache packages
packvault sync react vite tailwindcss

# Install later—even offline
packvault install react

Current Features

📦 Offline package installation
🔒 Integrity verification
📄 Lockfile-aware syncing
🚀 Offline project templates
💾 Portable package vaults

Coming Soon

🌐 LAN package sharing
🔄 Peer-to-peer synchronization
🖥️ Local registry server
🎓 Classroom mode

What I Learned

Building PackVault taught me much more than I expected.

I learned about:

CLI architecture
Package registries
Dependency resolution
File systems
Caching strategies
Software design

It started as a small side project but quickly became one of the most technically challenging things I've worked on.

I'd Love Your Feedback

I'm actively building PackVault and would love feedback from the community.

🌐 Website: https://pack-vault-website.vercel.app/

⭐ GitHub: https://github.com/Omnikon-Org/PackVault

If you've ever struggled with dependency management or offline development, I'd love to hear your thoughts.

Happy coding! 🚀

We Built the DemonDie Frontend Quiz Arena 2026 — Here’s Why

Rishi Bhardwaj — Wed, 24 Jun 2026 11:15:53 +0000

Building a tech community is not just about opening a GitHub organization, making a Discord server, or posting project updates online.

For us, it’s about creating real opportunities for students and developers to learn, compete, contribute, and grow together.

That’s exactly why we created the DemonDie Frontend Quiz Arena 2026 — a frontend quiz competition built for students, freshers, and developers who want to test their knowledge, challenge themselves, and become part of a practical developer community.

In this article, I want to share the story behind it:

why we created it,
what the event includes,
what we learned while building it,
and how it fits into the bigger vision of DemonDie.

What is DemonDie?

DemonDie is a community-driven tech organization focused on building useful projects, creating learning opportunities, encouraging open-source contribution, and helping developers grow through practical experiences.

Our goal is simple:

Build impactful projects
Create opportunities for students and developers
Encourage contribution and collaboration
Make learning more practical and community-driven

We don’t want DemonDie to be “just another org with a logo and a few repos.”
We want it to become a place where people can:

learn,
build,
compete,
contribute,
and get recognized for their work.

The Frontend Quiz Arena 2026 is one of the first major steps in that direction.

Why we created the Frontend Quiz Arena 2026

Frontend development is one of the most common entry points into tech.

A lot of students start with HTML, CSS, JavaScript, React, Git, and GitHub. They watch tutorials, build small projects, and slowly improve. But one thing is often missing: a fun way to actually test what they know.

We wanted to create something that would:

help people test their frontend fundamentals,
make learning more engaging through competition,
give students and developers a chance to challenge themselves,
introduce more people to the DemonDie community,
and create a small but meaningful event that people would genuinely enjoy participating in.

Instead of overcomplicating it, we decided to keep it simple, focused, and accessible.

That’s how the DemonDie Frontend Quiz Arena 2026 was born.

About the event

The DemonDie Frontend Quiz Arena 2026 is an online frontend quiz competition hosted on Unstop.

It is designed for students, freshers, and developers who want to test their frontend knowledge in a short, competitive format.

Event format

30 multiple-choice questions
30-minute quiz
Individual participation
No negative marking
Open to students, freshers, and developers

Topics covered

The quiz includes questions from:

HTML
CSS
JavaScript
React
Git
GitHub
Frontend best practices

We wanted the quiz to focus on concepts that actually matter in a frontend journey — not random trivia, but the kind of knowledge that helps someone become a better builder.

Why we thought this was worth building

A lot of people in tech communities consume content, but don’t always get enough opportunities to participate.

We wanted to build something that would be more interactive than a normal post and more approachable than a full hackathon.

A frontend quiz felt like the right starting point because:

it’s beginner-friendly,
it still tests real knowledge,
it doesn’t require a huge time commitment,
and it gives people a reason to engage with the community.

Even a small event like this can do a lot:

help someone discover what they know,
show them where they need to improve,
push them to learn more,
and make them feel like they’re part of something bigger than just another online course or tutorial.

What participants can gain from it

We wanted the event to offer more than just “attempt quiz and leave.”

1. A way to test frontend fundamentals

Many people learn by building projects, but they don’t always know how strong their fundamentals really are.
This quiz gives them a chance to check their understanding of core frontend concepts.

2. A reason to revise and learn

Competitions naturally push people to prepare.
Even if someone joins casually, the event can motivate them to revise topics like JavaScript, React, CSS, and Git in a more focused way.

3. Exposure to a growing community

Through this event, participants get introduced to DemonDie and the kind of ecosystem we want to build around projects, collaboration, open source, and developer growth.

4. Recognition

The winner receives a certificate from DemonDie, and top participants get visibility inside the community.

Why we chose Unstop

When we were planning the event, one of the biggest questions was where to host it.

We wanted a platform that:

was easy to access,
already had a student/developer audience,
could handle registrations smoothly,
and made the event feel structured and professional.

That’s why we chose Unstop.

Since this is one of DemonDie’s early public events, using a platform with an existing audience and event flow made a lot of sense. It allowed us to focus on the content, branding, and participant experience rather than building the hosting flow from scratch.

What building this event taught us

One of the best things about creating the DemonDie Frontend Quiz Arena 2026 is that it wasn’t just valuable for participants — it was also a learning experience for us as builders.

From deciding the format and writing the questions to creating banners, setting up the Unstop page, and preparing the event details, this turned into a full team effort.

It taught us a lot about:

planning a public event,
structuring content clearly,
building better branding around a launch,
presenting an organization professionally,
and coordinating work as a team.

It may look like “just a quiz” from the outside, but internally it helped us understand what it takes to create something people can actually participate in and enjoy.

What this means for DemonDie

For us, this quiz is much bigger than a single event.

It represents the kind of ecosystem we want DemonDie to become.

We want DemonDie to be a place where students and developers can find:

open-source opportunities,
practical projects,
community events,
roadmaps and learning resources,
collaboration opportunities,
and recognition for their work.

The Frontend Quiz Arena 2026 is one of the first public steps toward that vision.

We want to keep building things that are useful, engaging, and community-first — whether that’s quizzes, roadmaps, contributor programs, projects, or other developer-focused initiatives.

What’s next?

This is only the beginning.

We want to keep building DemonDie into a place where developers don’t just scroll, watch, or consume content — they participate, contribute, compete, and grow.

Some of the things we want to keep doing include:

more tech quizzes and competitions,
more open-source opportunities,
more project-based collaboration,
better learning resources,
and a stronger student/developer community around building.

If this event gets a strong response, we’d love to expand into more domains and create even bigger opportunities in the future.

Final thoughts

Starting anything is hard.

Launching the DemonDie Frontend Quiz Arena 2026 may look like a small step, but for us it represents something much bigger: the beginning of building the kind of developer community we believe in.

A community where people don’t just learn passively, but actively take part.
A community where students and developers can test themselves, contribute, build together, and get recognized for their effort.

We’re excited to see people join the quiz, challenge themselves, and become part of what we’re building with DemonDie.

And this is just the beginning.

See you in the arena. 🔥

Event details

Event: DemonDie Frontend Quiz Arena 2026
Format: Online frontend quiz
Duration: 30 minutes
Questions: 30 MCQs
Topics: HTML, CSS, JavaScript, React, Git, GitHub, frontend best practices
Participation: Individual
Reward: Winner certificate from DemonDie

devto #webdev #frontend #javascript #react #opensource #community #students #career #github

Building SyncCanvas: An AI-Powered Real-Time Collaborative Whiteboard

Rishi Bhardwaj — Fri, 19 Jun 2026 21:10:21 +0000

Modern collaboration needs more than documents and chat messages. Teams need a shared visual space where ideas can be created, organized, and refined together in real time.

That's why I built SyncCanvas — an AI-powered collaborative whiteboard that combines real-time multiplayer collaboration, infinite canvas drawing, and AI-assisted brainstorming into one modern workspace.

The Problem

Most collaboration tools focus on only one aspect of teamwork.

Some are great for drawing. Others are excellent for documentation. AI tools often live in separate windows, disconnected from the creative workflow.

I wanted a platform where teams could brainstorm visually while AI actively helped generate and organize ideas directly on the canvas.

Introducing SyncCanvas

SyncCanvas is an infinite multiplayer whiteboard designed for students, developers, teams, and creators.

Key features include:

Real-time collaboration with live synchronization
Infinite canvas with pan and zoom
Drawing tools, shapes, text, and sticky notes
AI-powered content generation using Gemini
Private room sharing
Guest mode access
PNG export support
WiFi Rooms for local collaboration
Real-Time Collaboration

Collaboration is at the heart of SyncCanvas.

Using Yjs and WebSockets, multiple users can work on the same board simultaneously while seeing updates instantly.

Users can:

View live cursors
Track online participants
Join private rooms using secure room codes
Collaborate anonymously through guest mode

This creates a seamless experience similar to working together in the same room.

Infinite Canvas Experience

The whiteboard is designed to be limitless.

Users can:

Draw freehand sketches
Create rectangles and circles
Add text elements
Organize ideas with sticky notes
Move freely across an infinite workspace
Export workspaces as images

The canvas is powered by Fabric.js, providing smooth rendering and flexibility for future enhancements.

AI-Powered Brainstorming

One of the most exciting features is the integration of Gemini AI.

Instead of manually creating diagrams, users can simply enter prompts such as:

Generate a mind map for machine learning

The AI automatically creates structured visual elements directly on the board, helping users turn ideas into organized diagrams within seconds.

This transforms the whiteboard from a drawing tool into an intelligent brainstorming assistant.

WiFi Rooms

SyncCanvas introduces a unique feature called WiFi Rooms.

Anyone connected to the same physical network can instantly join a shared workspace without exchanging links or room codes.

This feature is particularly useful for:

Classrooms
Study groups
Hackathons
Team meetings
Workshops

It removes friction and makes local collaboration effortless.

Tech Stack
Frontend
React 19
Vite
Tailwind CSS v4
Framer Motion
Collaboration
Yjs
y-websocket
Canvas Engine
Fabric.js
Backend
Node.js
Express.js
Database & Authentication
Firebase Firestore
Firebase Authentication
Challenges During Development

Building a real-time collaborative application comes with several challenges.

State Synchronization

Keeping every user's canvas perfectly synchronized required careful handling of collaborative state management and conflict resolution.

AI Canvas Generation

Transforming AI responses into meaningful visual structures required designing a system that converts text output into organized graphical elements.

Performance

Supporting multiple users, large canvases, and continuous updates while maintaining smooth interactions demanded significant optimization.

What's Next?

Future plans for SyncCanvas include:

Voice collaboration
AI-generated flowcharts
Team workspaces
Version history
SVG and PDF exports
Presentation mode
More advanced AI tools
Open Source Contributions Welcome

SyncCanvas is open to contributions from developers who are interested in:

Frontend development
Real-time systems
AI integrations
UI/UX improvements
Performance optimization

Every contribution helps make the platform better for the community.

Final Thoughts

Building SyncCanvas has been an incredible learning experience in real-time collaboration, AI integration, and modern web development.

The goal was never just to create another whiteboard.

The goal was to create a space where people can think together, build together, and transform ideas into reality faster than ever before.

If you're interested in collaborative software, AI-powered productivity tools, or open-source development, I'd love to hear your feedback.

Happy building! 🚀

opensource #react #javascript #webdev #ai #firebase #nodejs #collaboration

PackVault: Cache npm Packages Once. Install Forever — Even Offline.

Rishi Bhardwaj — Wed, 17 Jun 2026 09:14:23 +0000

Most developers don't think about package installation until the internet goes down.

Whether you're on a flight, in a classroom, behind a restricted firewall, or simply dealing with poor connectivity, modern JavaScript development becomes surprisingly difficult when npm isn't reachable.

That's exactly why I built PackVault.

What is PackVault?

PackVault is an offline-first package caching and distribution CLI for JavaScript developers.

It allows you to:

✅ Cache npm packages locally
✅ Install packages without internet access
✅ Share dependencies across your LAN
✅ Create projects offline using templates
✅ Synchronize packages between machines
✅ Verify package integrity and security

Simply sync once:

packvault sync react vite tailwindcss

And later install from your local vault:

packvault install react

No internet required.

The Problem

Every developer downloads the same dependencies repeatedly.

React
Vite
Tailwind CSS
Express
Next.js

Thousands of developers fetch identical packages every day.

This results in:

Wasted bandwidth
Slower project setup
Dependency on npm availability
Frustrating experiences in low-connectivity environments

PackVault turns downloaded dependencies into reusable assets instead of temporary downloads.

Key Features

📦 Offline Package Management

Cache packages once and install them forever.

Lockfile-aware syncing
npm, Yarn, and pnpm support
SemVer-aware installs
Dependency caching
Incremental synchronization

🌐 LAN Package Sharing

Share packages with teammates and classrooms.

packvault share

One machine downloads.

Everyone else benefits.

⚡ Peer-to-Peer Synchronization

Discover and sync package vaults directly between devices.

packvault discover
packvault connect 192.168.1.25

🚀 Offline Project Creation

Create projects without touching the internet.

packvault create react my-app
packvault create nextjs web-app
packvault create astro docs-site

🔒 Security First

PackVault includes:

SHA-512 integrity verification
Offline vulnerability auditing
Package allowlists and blocklists
Authenticated peer synchronization
Audit logging

Real-World Use Cases

Students

Learn and build projects without worrying about unstable internet connections.

Workshops & Bootcamps

Distribute one package vault instead of making every participant download dependencies.

Teams

Reduce bandwidth consumption and accelerate onboarding.

Air-Gapped Environments

Build software in completely isolated systems.

Remote Developers

Prepare dependencies before travel and continue working anywhere.

Why I Built It

As a student developer and open-source builder, I noticed how often development workflows break because of connectivity issues.

The idea behind PackVault was simple:

If I already downloaded a package once, I should never need to download it again.

That small idea evolved into a complete offline-first package infrastructure platform.

The Vision

PackVault isn't trying to replace npm.

It's trying to make developers less dependent on constant internet access.

Future plans include:

Enhanced registry mirroring
Differential peer synchronization
Smarter dependency graph analysis
Multi-user vault support
Better management interfaces

The goal is simple:

Build software anywhere, anytime, regardless of connectivity.

Try PackVault

⭐ GitHub: https://github.com/Demon-Die/PackVault

📦 npm: https://www.npmjs.com/package/packvault

If you find the project interesting, consider giving it a star and sharing feedback.

Built by Rishi Bhardwaj under DemonDie Organization.

Cache npm packages once. Install forever — even offline.

Introducing UnVibe: Because AI Shouldn't Be Your Crutch

Rishi Bhardwaj — Tue, 16 Jun 2026 18:12:09 +0000

Built by Sharanyo Banerjee under DemonDie Organization.
Repo Link : https://github.com/Demon-Die/UnVibe

The Problem Nobody Wants to Admit

We're entering a strange era of software development.

Developers have access to the most powerful coding assistants ever created. In seconds, AI can generate components, APIs, database schemas, algorithms, and even complete applications.

That's incredible.

But it has also created a problem.

Many developers today are becoming better at writing prompts than understanding code.

A growing number of people can generate solutions, yet struggle to explain how those solutions actually work.

And that's dangerous.

Because when the AI is wrong, the bugs appear, or the system reaches production scale, understanding matters far more than generation.

The industry doesn't need more people who can copy code.

It needs people who can think.

That's why we started building UnVibe.

What Is UnVibe?

UnVibe is an open-source learning platform designed for the AI era.

Not a platform that teaches you how to use AI.

A platform that teaches you how to stay valuable despite AI.

Its philosophy is simple:

Don't use AI as a crutch. Use it as a benchmark.

Instead of asking users to generate solutions, UnVibe forces them to understand them.

The goal isn't faster learning.

The goal is deeper learning.

The Decode → Rebuild → Defend Framework

At the core of UnVibe is a learning loop built around three stages.

Decode

The platform generates a production-grade solution to a real-world problem.

Before touching the keyboard, the learner must understand it.

They annotate the code, answer questions about it, and prove they understand what's happening beneath the surface.

No skipping.

No guessing.

No pretending.

Rebuild

Once the code is understood, the learner rewrites it from scratch.

No AI assistance.

No copy-pasting.

No shortcuts.

The objective is to recreate the solution through understanding rather than memory.

Because if you truly understand something, you should be able to build it yourself.

Defend

This is where most learning platforms stop.

UnVibe doesn't.

The platform periodically brings back previous work and challenges users to explain, modify, optimize, or debug it.

The learner must defend their decisions.

Just like they would during a technical interview.

Or a code review.

Or a production incident.

Understanding that can't survive questioning isn't understanding at all.

Why Existing Platforms Aren't Enough

Most coding platforms focus on one thing:

Completion.

Finish a challenge.

Finish a course.

Finish a project.

But completing something doesn't mean understanding it.

You can watch an entire tutorial and forget it the next day.

You can copy a project and never learn the underlying concepts.

You can generate code with AI and never know why it works.

UnVibe is built around retention, explanation, and understanding.

Not completion.

Measuring What Actually Matters

One of the most exciting parts of UnVibe is the Irreplaceability Score (IRS).

Most platforms measure:

Problems solved
Streaks maintained
Hours spent learning

We wanted to measure something more meaningful.

The IRS evaluates how deeply a developer understands code compared to how much they rely on generated solutions.

It evolves through:

Decode performance
Rebuild quality
Defend accuracy
Long-term retention

The purpose isn't competition.

The purpose is growth.

Building Developers for the Future

The software industry is changing rapidly.

AI will continue getting better.

Code generation will become easier.

Boilerplate will become automated.

Simple development tasks will become commodities.

The valuable developers won't be the ones who can generate code the fastest.

They'll be the ones who can:

Understand complex systems
Make architectural decisions
Explain tradeoffs
Debug production failures
Learn continuously

Those skills remain valuable regardless of how powerful AI becomes.

That's what UnVibe is designed to strengthen.

Why We're Open Source

We believe education improves when communities build it together.

That's why UnVibe is being developed as an open-source project.

We want contributors, educators, students, and developers to help shape what learning should look like in the AI era.

The challenge we're solving isn't just technical.

It's educational.

And it's a problem that affects every developer.

What's Next?

We're currently building the foundation of UnVibe, including:

Decode modules
Rebuild challenges
Defend sessions
AI-powered assessments
Irreplaceability Score tracking
Learning dashboards

And this is only the beginning.

Our vision is to create a platform where developers don't simply consume information—they prove understanding.

Final Thoughts

AI isn't the enemy.

Blind dependency is.

The future belongs to developers who know how to think, adapt, and understand.

UnVibe exists to help build those developers.

If AI can generate the code, your value comes from understanding it better than anyone else.

And that's exactly what we're trying to teach.

Built by Sharanyo Banerjee
Supported by DemonDie Organization

Stop vibing. Start understanding.

Why Most Students Never Make Their First Open-Source Contribution

Rishi Bhardwaj — Tue, 09 Jun 2026 19:31:17 +0000

A few years ago, I thought contributing to open source was something only experienced developers did.

I would look at large repositories, thousands of lines of code, hundreds of contributors, and immediately think:

"I'm not good enough for this."

If you're a student or beginner developer, you've probably felt the same way.

The interesting thing is that most aspiring contributors don't fail because they lack technical skills.

They never start.

The Fear of Breaking Something

One of the biggest barriers to open source is fear.

Fear of:

Making mistakes
Asking "stupid" questions
Submitting a bad pull request
Looking inexperienced

The reality is that every experienced contributor started exactly where you are.

Nobody was born knowing Git, GitHub, pull requests, or code reviews.

The Tutorial Trap

Many students spend months watching tutorials.

Tutorial after tutorial.
Course after course.

The problem?

Learning without building creates a false sense of progress.

You feel productive, but you're not solving real problems.

Open source forces you to:

Read unfamiliar code
Communicate with other developers
Solve actual issues
Learn independently

Those are skills tutorials rarely teach.

Why Open Source Matters

Open source is more than free software.

It's one of the best ways to:

Gain real-world experience
Improve problem-solving skills
Learn collaboration
Build a public portfolio
Connect with developers around the world

Every contribution, no matter how small, teaches something valuable.

Your First Contribution Doesn't Need to Be Code

This is something many beginners don't realize.

You can contribute by:

Improving documentation
Fixing typos
Creating tutorials
Testing features
Reporting bugs
Reviewing pull requests

Every project needs more than developers.

It needs contributors.

How to Start Today

Find a project you genuinely care about.
Look for beginner-friendly issues.
Read the contribution guidelines.
Ask questions when you're stuck.
Submit your first pull request.

Don't focus on making a huge contribution.

Focus on making your first contribution.

Final Thoughts

The biggest obstacle to open source isn't technology.

It's taking the first step.

Your first pull request won't be perfect.

Your first issue might be confusing.

Your first contribution might be tiny.

That's okay.

What matters is getting started.

Because every experienced contributor was once a beginner who decided to click "Fork" for the first time.

What was your first open-source contribution?

I'd love to hear your story in the comments.