Skip to content

Remove Webpack and replace with more native tooling (JS, SCSS, TypeScript) #909

@sebastianthulin

Description

@sebastianthulin

We should remove Webpack as our build tool and replace it with a more modern, native tooling setup.
The goal is to simplify our build process, improve performance, and reduce dependency bloat.

The new setup should support:

  • JavaScript (ES modules, transpilation where needed)
  • TypeScript (type checking + compilation)
  • SCSS (compilation to CSS, autoprefixing, minification)
  • Other present languages and solutions.

Motivation

  • Webpack is heavier than needed for our current setup.
  • Native tools offer faster builds, easier configuration, and better ESM support.
  • Fewer dependencies → faster CI/CD.

Acceptance Criteria

  • Webpack is fully removed from the project.
  • New build pipeline implemented using modern tooling.
  • JS, TS, and SCSS files are built and optimized for production.
  • Development server with hot-reload support is available.
  • CI/CD updated to work with the new build process.
  • Documentation updated to reflect the new tooling and commands.
  • Cashbusting logic (manifest.json) is still present and works the same way.

Notes

  • Ensure backward compatibility with existing import paths.
  • Keep build output structure consistent to avoid breaking deployment scripts.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions