webpack - CodingKiwi

webpack

A collection of 5 posts

Benchmarking vite vs webpack

Benchmarking vite vs webpack

I still use Webpack for most of my projects, but Vite is rapidly becoming the standard build tool. As I mentioned in earlier posts, I still encounter a few issues with it: Why I’m not switching to vite yetTwisted paths While searching for a markdown based Static-Site Generation (SSG)

developing shared npm packages locally

developing shared npm packages locally

My second post on this blog was about how complicated it seems to be to develop shared npm packages locally. I decided to take another crack at finding a better workflow. The situation is more or less the same, I have hop, my scss/vue component library which I use

1 year later - state of vuepress and vite

1 year later - state of vuepress and vite

In my post Why I'm not switching to vite yet almost exactly a year ago I explained why switching to vite was not an option to me yet. Some things have changed so let's check again! vitepress and vuepress As stated on the website, they have

Vue Component Workbench

Vue Component Workbench

In my projects I've been using my vue/scss framework "hop". Whenever I add new components or change something, it is quite helpful to have an instance of webpack running inside the hop project to see my changes in realtime instead of publishing a new version

Why I'm not switching to vite yet

Why I'm not switching to vite yet

Twisted paths While searching for a markdown based Static-Site Generation (SSG) to build a documentation page I came across vuepress, first I started with vuepress 1 but since I wanted to install it in my existing project (which uses vue 3 and vuepress 1 does not support vue 3) I