Debugging and aurelia alameda

Hi, guys.

I am working on a new app and tried the alameda bundler. In previous works I have used webpack.
Using typescript as development language.

When debugging, in chrome’s source code window, I see the transpiled code:

But when I used webpack, sourcemaps were generated so the debugging was easier, accessing the original typescript source code.

Does anyone know if there’s a solution for this?

Thanks for any help. Take care!

1 Like

You should see the .ts source there as well if the map is setup correctly. I just recently setup a new project with cli 1.3.* and using the builtin bundler and Alameda. Had no issue, and no changes needing to be made for it to work.

Errors will show up pointing to the bundle in the console, but I think it should redirect to the .ts source I think.

Is that no happening for you?

1 Like

Hi, thanks for your answer.
Looks like my project is corrupt in some way, because the chrome console shows that the sourcemaps are not being loaded.
I had to make a new project and copy source files there, and the issue is gone.
Sad thing is that I wasn’t able to determine what went bad.

thank you for your help.

1 Like