Skip to content
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

Sourcemap support #20

Open
kenguest opened this issue Nov 16, 2023 · 1 comment
Open

Sourcemap support #20

kenguest opened this issue Nov 16, 2023 · 1 comment

Comments

@kenguest
Copy link

Are there plans to generate sourcemaps ( https://web.dev/articles/source-maps & https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit?pli=1#heading=h.1ce2c87bpj24 ) so that when debugging through an assembled file created by gulp-kit the browser/ide knows which smaller file the code came from and opens the correct one at the right line?

Having this would be fantastic.

@fatso83
Copy link
Contributor

fatso83 commented Nov 17, 2023

Seeing that the last commit was five years ago, I am not thinking there are plans to add it, but I am guessing there's a high probability Jeremy would accept a PR that adds the feature 😉 I had a look at the spec, and the scariest bit was the VLQ encoding stuff, but I found a Node library that takes care of this, so it should be totally doable. If you got an itch to scratch ...

(I haven't used *.kit or Codekit files since 2014, so this is for someone else)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants