# 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:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![estaylorco](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/estaylorco/32/1887_2.png) [@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")

</div>

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.

---

_[View the full topic](https://discourse.aurelia.io/t/au-2-0rc-default-vite-babel-skeleton-uses-vite-6-0-3-displaced-breakpoints/6573)._