# Au 2.0RC: Default Vite/Babel skeleton uses Vite 6.0.3; displaced breakpoints
**URL:** https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573
**Category:** Help Requests
**Created:** [January 18, 2026, 1:28am UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573 "2026-01-18T01:28:26Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [January 18, 2026, 1:28am UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/1 "2026-01-18T01:28:26Z")
Hello Everyone,
_In the spirit of firing up Au 2.0RC…_
I just ran `npx makes aurelia` with the following configuration (copied from the terminal):
`npx makes aurelia new-project-name -s babel,vitest`
and Vite 6.0.3 is installed, not Vite 7. These are the relevant bits of the package.json file:
```auto
"dependencies": {
"aurelia": "latest",
"@aurelia/router": "latest"
},
"devDependencies": {
"eslint": "^9.17.0",
"globals": "^15.14.0",
"@aurelia/testing": "latest",
"stylelint": "^16.12.0",
"stylelint-config-standard": "^36.0.1",
"@aurelia/vite-plugin": "latest",
"vite": "^6.0.3",
"vite-plugin-node-polyfills": "^0.22.0",
"vite-plugin-babel": "^1.3.0",
"vitest": "^2.1.8",
"jsdom": "^25.0.1",
"@babel/plugin-proposal-decorators": "^7.25.9",
"@babel/plugin-syntax-dynamic-import": "^7.8.3",
"@babel/core": "^7.26.0",
"@babel/preset-env": "^7.26.0",
"@babel/eslint-parser": "^7.25.9"
},
...
"type": "module",
"overrides": {
"vite-plugin-node-polyfills": {
"vite": "^6.0.0"
}
}
```
Should we not be running Vite 7?
**Also, I am still unable to configure a launch file that is compatible with this skeleton in that breakpoints are still displaced** , as I indicated in this post a year ago: [Default Aurelia app scaffolding (first "makes" option) produces displaced breakpoints under Vite](https://discourse.aurelia.io/t/default-aurelia-app-scaffolding-first-makes-option-produces-displaced-breakpoints-under-vite/6318) .
I followed the advice/discourse of @huochunpeng and @davidsk once again, and I’m still unable to make this work. Breakpoints are displaced in both vscode and in devtools.
It’s really starting to bum me out that the only configuration I can get to work is the Webpack/Babel configuration. I have abandoned the idea of being able to continue with the babel-contracts-plugin; I should move forward with Vite, and I’m good with that.
I completely uninstalled vscode, right out to the folders on my Mac, and then reinstalled it. I tried again before any extensions were installed. Still no luck. Also, my Mac is relatively new, used primarily for development.
What on earth could be the problem?
---
### Author:  [@elitemike](https://discourse.aurelia.io/u/elitemike)
#### Post date: [January 19, 2026, 3:19pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/2 "2026-01-19T15:19:59Z")
I meant to point out the vite version to someone. Upgrading to 7 should be no issue if you can actually get your project to run.
Regarding the launch file. I was able to get breakpoints working with a PNPM workspace running in WSL using Claude sonnet, definitely let AI help you if you can. I am using typescript though which I think makes things easier.
I thankfully don’t have to have babel in my project and if I use a package that isn’t typescript, I’m going through a conversion process if I can.
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [January 19, 2026, 5:28pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/3 "2026-01-19T17:28:39Z")
I’m trying to determine if it’s significant that the skeletons are still pointing to Vite 6. And Vite/Babel is one of the supported options on `makes`.
I don’t embrace TS or AI, so I can’t really take your setup as an example.
I have a vanilla vscode setup on a relatively new Mac meant primarily for development. Nothing exotic.
I just don’t understand why there would there be problems with breakpoints? If the skeletons need to harmonize with a launch file, I would say we need to know how so.
---
### Author:  [@elitemike](https://discourse.aurelia.io/u/elitemike)
#### Post date: [January 19, 2026, 5:55pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/4 "2026-01-19T17:55:57Z")
What does vs code show when you hover over the breakpoint and look at why the breakpoints can’t be hit?
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [January 19, 2026, 5:59pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/5 "2026-01-19T17:59:50Z")
The breakpoints do show that they can be hit, but they’re displaced. I illustrate the problem in this post: [Default Aurelia app scaffolding (first "makes" option) produces displaced breakpoints under Vite](https://discourse.aurelia.io/t/default-aurelia-app-scaffolding-first-makes-option-produces-displaced-breakpoints-under-vite/6318) .
This problem telegraphs out to devTools as well, which tells me it has something to do with sourcemaps.
But for the life of me, I haven’t been able to hit upon a skeleton/launch config that solves the problem.
---
### Author:  [@elitemike](https://discourse.aurelia.io/u/elitemike)
#### Post date: [January 19, 2026, 6:05pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/6 "2026-01-19T18:05:10Z")
I would need to experiment a bit, but one thing the AI had me change was to actually add this to the viteconfig. Once upon a time I feel like I did run into the issue you are describing, but most of my issues have been centered around packages in the workspace. Quickly looking at your other post, I didn’t see that in your config
````auto
build: {
sourcemap: true,
}```
````
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [January 19, 2026, 6:11pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/7 "2026-01-19T18:11:36Z")
That was one of the first things I changed. Doesn’t solve the problem. Breakpoints are still displaced.
---
### Author:  [@dwaynecharrington](https://discourse.aurelia.io/u/dwaynecharrington)
#### Post date: [January 19, 2026, 11:37pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/8 "2026-01-19T23:37:05Z")
I’ve got a PR which updates Vite, Babel and other dependencies with the makes CLI that should be in soon.
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [January 19, 2026, 11:41pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/9 "2026-01-19T23:41:41Z")
Excellent! I love WebPack, but I need to get onto Vite/Babel. So that’s great news!
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [February 18, 2026, 2:42am UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/10 "2026-02-18T02:42:37Z")
Hello @dwaynecharrington ,
I just thought I’d update you on this.
I ran `npx makes aurelia` again, choosing Vite and Babel with basic routing, no other features, **and it looks like the displaced breakpoints problem is solved!** I can now set breakpoints like a normal person 🙂 !
However, if I make a simple change to welcome-page.js, hit save, and then bring up devTools, this is what I see in the console:
This problem was there before, but someone else had raised the issue, claiming it was occuring with every other save (which it was at that time as I had the same problem).
Has there been any progress on this, or at least a guess as to what it is?
---
### Author:  [@ghiscoding](https://discourse.aurelia.io/u/ghiscoding)
#### Post date: [February 23, 2026, 8:51pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/11 "2026-02-23T20:51:45Z")
I think the issue you’re talking is related to these links:
- issue #2365 - [Aurelia Vite Plugin HMR still fails every second edit · Issue #2365 · aurelia/aurelia](https://github.com/aurelia/aurelia/issues/2365)
- fixed by PR #2378 - [fix(hmr): state capture over edits by Sayan751 · Pull Request #2378 · aurelia/aurelia](https://github.com/aurelia/aurelia/pull/2378)
Even if it was merged, I don’t think it was released yet
---
### Author:  [@estaylorco](https://discourse.aurelia.io/u/estaylorco)
#### Post date: [February 23, 2026, 8:54pm UTC](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573/12 "2026-02-23T20:54:18Z")
Thanks, @ghiscoding ! Those issues _are_ related.
I’ll just bide my time, then. The issue isn’t holding up migration as I’m using Webpack/Babel at the moment.