-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorrect sourcemaps off by a couple lines #163
Comments
I think this might be fixed in the react-router-devtools, I'll definitely check this out with them to see if it works properly. Thank you so much for the detailed repro! |
Thank you very much for the super fast response!! At your service! |
Hey @lhapaipai would you mind checking if this is still an issue with react-router-devtools and react router v7, I completely changed the approach and it should not augment source maps anymore |
Hi @AlemTuzlak, unfortunately the issue still exists with react-router v7 and react-router-devtools environment same as above:
my package.json {
"name": "react-router-v7-hw",
"private": true,
"type": "module",
"scripts": {
"build": "react-router build",
"dev": "react-router dev",
"start": "react-router-serve ./build/server/index.js",
"typecheck": "react-router typegen && tsc --build --noEmit"
},
"dependencies": {
"@react-router/node": "^7.0.1",
"@react-router/serve": "^7.0.1",
"isbot": "^5.1.17",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-router": "^7.0.1"
},
"devDependencies": {
"@react-router/dev": "^7.0.1",
"@types/node": "^20",
"@types/react": "^18.3.12",
"@types/react-dom": "^18.3.1",
"autoprefixer": "^10.4.20",
"postcss": "^8.4.49",
"react-router-devtools": "^1.0.4",
"tailwindcss": "^3.4.15",
"typescript": "^5.6.3",
"vite": "^5.4.11",
"vite-tsconfig-paths": "^5.1.2"
}
} I took the same example as above. My breakpoints are in the loader function of the import type { Route } from "./+types/root";
export async function loader({ request }: Route.LoaderArgs) {
let foo = "bar";
foo = "baz";
return {
foo,
};
} the example in video react-router-v7-sans-audio.mp4Do not hesitate if you want more informations |
Thank you so much, I'll look into this the first chance I get 🫡 |
Hi,
Thank you very much for this amazing plugin !!!
However, I encounter offsets in the sourcemaps that make Remix debugging with vscode complicated. By activating/deactivating your plugin, I realized that it was the plugin that was causing it.
environnement:
Reproduction
Here is a minimal example to reproduce the issue.
pnpm create remix
pnpm add remix-development-tools
add the plugin into vite config
add a loader into the
app/root.tsx
Use
VSCode
to debug this app.add a "Attach by Process ID" debugging method for vscode at
.vscode/launch.json
run
pnpm run dev
start debugging and add a breakpoint at
return null
of theapp/root.tsx
loader function (line 14 in the screenshot)browse
http://localhost:5173
the breakpoint is not reached
if on the other hand we move our breakpoint a little lower in the code (line 18 in the screenshot). we notice that the breakpoint is reached but the inspection corresponds to 4 lines above. we have our
hello = 'world'
if we remove the
remix-development-tools
plugin in the vite.config.jsstart debugging and add a breakpoint at
return null
of the loader function (line 14 in the screenshot)everything working fine
I hope I have been as clear as possible, do not hesitate if you would like more information.
have a great evening
The text was updated successfully, but these errors were encountered: