salman asif.
The Kinetic Garden

Find your way.

← ALL WORK / Platform

A faster path forward.

A compatibility-first Rsbuild/Rspack proof of concept for an established Vue 2 platform.

ROLESenior Software Engineer
CONTEXTSecuriti.ai
PERIOD2024–2025
STATUSProof of concept
VueRsbuildRspackWebpackDockerKubernetes
01 / CONTEXT

The problem underneath.

Legacy build tooling creates friction well beyond compilation. Changing it can affect asynchronous imports, routing, assets, development workflows, and production delivery. The goal was to evaluate a better path without destabilizing the application.

02 / REALITY

What shaped the solution.

  • An established Vue 2 application on Webpack 4.
  • Existing route, asset, and async import behavior had to remain compatible.
  • Docker/Kubernetes environments and release verification added constraints beyond a local build.
03 / ENGINEERING JUDGMENT

The important decisions.

01

Prove compatibility before promising migration.

I led a Rsbuild/Rspack proof of concept around the existing application. Runtime behavior, routing, asset handling, and async imports were explicit validation targets.

02

Test the environment as well as the code.

Build and deployment checks covered environment-specific behavior and regression risks, with smoke verification and release troubleshooting supporting confidence.

03

Keep the change surface small.

The effort focused on a lower-risk modernization path around the existing product rather than requiring a simultaneous framework rewrite.

04 / THE CONNECTIONS

A simpler view of the system.

  1. Existing Vue application
  2. Compatibility layer
  3. Rsbuild / Rspack
  4. Runtime verification
  5. Deployment checks

Conceptual flow. Simplified to explain the engineering without exposing internal implementation.

05 / OWNERSHIP

Where I made a difference.

I led the bundler compatibility proof of concept and supported build validation, deployment checks, regression fixes, and release verification.

06 / WHAT CHANGED

The result.

The proof of concept established a lower-risk path for modernizing a legacy build system. It is presented as compatibility work, with no unverified speedup or production migration claims.

07 / NEXT ITERATION

What I’d explore next.

A next iteration should publish repeatable cold-build, incremental-build, and runtime baselines across identical environments before selecting the final rollout strategy.

Architecture is deliberately simplified. This work was a proof of concept, not a claimed completed production migration.

NEXT SYSTEM

CargoBarn

Make yourself at home

Your kind of garden.

15 ways to make it yours. Your choice stays with you.

Make an entrance

Choose how your next style arrives.

Applied when you choose a style. Instant with Motion off or reduced motion.

Visual style

Choose a look to transform the whole page. This panel closes so you can explore it.

Liquid Glass becomes frosted glass with motion off. Parallax adds depth as you scroll.

Prefer a straight read? Recruiter view
Light color palette

Your light and dark choices are saved separately.

Dark color palette

Your light and dark choices are saved separately.