Debugging meteor with sourcemaps: package-name with colons crash discovery about vscode-node-debug HOT 6 CLOSED

Can you use sourceMapPathOverrides to add a mapping from ...foo:bar... to ...foo-bar... or however it is?

from vscode-node-debug.

Wohoo! You really prepared for a lot of generated-framework-source sh*t features 🎉

I added two mappings and it works like a charm:

"sourceMapPathOverrides": {
	"meteor://💻app/packages/assistify:*": "${workspaceFolder}/packages/assistify-*",
	"meteor://💻app/packages/rocketchat:*": "${workspaceFolder}/packages/rocketchat-*"
}

Thanks a ton, saved me a lot of frustration!

Oliver

P.s.: I'd be delighted if you supported regex in addition to glob with parameters which can be used at the replacing side.

from vscode-node-debug.

What version of Meteor are you using? We had some issues, which were resolved in 1.6, that triggers me ud to write this guide: https://github.com/Microsoft/vscode-recipes/tree/master/meteor

from vscode-node-debug.

@auchenberg we’re using Meteor 1.6.0.1 at this vier moment and node 8.9.4.
i know the short guide (thanks a ton) and also tried those very intuitive launch configurable (which made me think that you somehow had to do a lot specificall for Meteor).
I also successfully debugged the sample app.
I really think it has to do something with the colons. I’ll try just renaming the folder on the disk and revert to you afterwards, this will verify/falsify my hypothesis

from vscode-node-debug.

yup - verified 🎉

I renamed the package in the package-definition to that it matches the path on disk to assistify-ai.
Now, a breakpoint in a server-side-file of this packages turned red and the debugger stops as expected.

One could argue this not being an issue of the debugger but more a systematic issue of the environment. And I couldn't disagree much. However, this problem is widespread due to historic reasons which are still a recommendation:

But wait, what's up with the colon convention in the demo?
Prior to Meteor v1.1.0, Meteor used to create packages using the colon syntax to match how it references packages on the package server. As v1.1.0 introduced Windows support, they had to drop the colon syntax when creating folders as Windows machines don't support it. Bonk. Keep in mind: you still add packages using the colon syntax in your terminal like meteor add author:package.

So a bit of heuristic on finding the proper file (once the one guessed is not found in _findGeneratedToSourceMapping). It's really about the colon. Assuming the map states package:name, the target file usually resides in a folder called either package-name or simply name. Do you think this is manageable?

Renaming the folders is not an option since this was very disruptive to the code base :(

from vscode-node-debug.

Glad that worked, yeah regex replace would help in this situation, but that level of control isn't often needed.

from vscode-node-debug.