Tooling migrations don't have to take weeks anymore
I used to block out weeks for tooling migrations. Now I let Claude Code run in the background, check in when it's done, and pair with it to understand what changed.
Before you begin, make sure you have node and npm installed. Use a node version higher than 6. Also, note that all terminal commands are for Mac. Please use the equivalent commands for your OS.
The repository for this tutorial lives here
The other day I was setting up a D3.js project when I ran into the classic developer conundrum — if I wanted to set up the project without using a CDN, I’d need to learn a couple of other auxiliary technologies. I had been meaning to learn to use webpack anyways, so I was happy to find a reason to get a jump on it. I didn’t find an existing tutorial for these three technologies, so thought I would share how I set up my project with you!
Here we go!
npm init into your terminal.Follow the steps that appear on your screen. For the sake of this tutorial, it’s perfectly fine to use the defaults each time. Once you have done that, take a look at your package.json file. This is what mine looks like:
Yours should look similar, but with whatever information you have inputted, rather than the information I inputted!
npm install webpack webpack-dev-server into your terminal.touch webpack.config.js into your terminal.webpack.config.js file.As you can see above, you’ve specified an entry and an output.
index.js file that lives inside of a src folder.npm install --save-dev babel-cli into your terminal.package.json file will look like this:package.json file: "build": "babel src -d lib". It should look like this:Run npm build.
Next, type npm install babel-loader babel-core babel-preset-es2015. This will allow us to load all of the dependencies we need to get this working.
We will then need to create a .babelrc file. To do so, type touch .babelrc into your terminal.
Type npm install babel-preset-env --save-dev into your terminal and add these lines to your .babelrc file.
src by typing mkdir src in your terminal.src folder. If you’re on a mac, you can cd into your src file and then create an index.js and an index.html file with the command touch index.js index.html.index.js file, add a console.log to test if it is working later.!DOCTYPE to your index.html file. I’ve also added an <h1> tag with the word “Hi” in it. My index.html file looks like this:npm install html-webpack-plugin.webpack.config.js file.1 Head into your package.json file and add a start script to your npm scripts. Inside of scripts replace the line that begins with "test" and replace it with: "start": “webpack-dev-server". It will look like this:
npm start. Your app should start running. Check in your browser to make sure everything is working correctly.npm install d3 in your terminal.index.html file:You should see this in your browser:

In your index.js file, add an import statement to include D3 in the file: import * as d3 from 'd3';.
To test to be sure that D3 is loaded correctly, try using it by changing the color of the three rectangles you see on your screen. You can copy and paste the code below into your index.js file.
If you’ve done it correctly, you should see the three little squares turn orange!

If you’ve followed all of these steps, you should find that you now have Webpack, Babel, and D3 correctly installed and functional. Please comment below if you have any questions or run into any issues.
Sources
I used to block out weeks for tooling migrations. Now I let Claude Code run in the background, check in when it's done, and pair with it to understand what changed.
Frontend technical debt doesn't just slow down developers. It undermines your entire business through user attrition, legal risks, and revenue loss. Here's how to spot and communicate these hidden costs.
How I used Conductor and Claude to streamline my team's Dependabot review workflow — and how a colleague turned it into a GitHub Action