Originally at 2014-09-15T14:16:51Z by Herbert Vojčík
In the present state, .js files contain some data that is aimed at IDE (source, class references) not otherwise used in the runtime. This info is obtainable by reading .st file and parsing it.
Proposal is to not include IDE info in .js files at all, instead let IDEs (and other tools) load this data lazily - probably not by themselves, but using some IDE-helper code for that in Amber itself.
Originally at 2014-09-15T14:16:51Z by Herbert Vojčík
In the present state, `.js` files contain some data that is aimed at IDE (source, class references) not otherwise used in the runtime. This info is obtainable by reading `.st` file and parsing it.
Proposal is to not include IDE info in `.js` files at all, instead let IDEs (and other tools) load this data lazily - probably not by themselves, but using some IDE-helper code for that in Amber itself.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4378942-do-not-include-ide-info-in-compiled-js-derive-it-from-st?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Originally at 2014-09-15T14:16:51Z by Herbert Vojčík
In the present state,
.js
files contain some data that is aimed at IDE (source, class references) not otherwise used in the runtime. This info is obtainable by reading.st
file and parsing it.Proposal is to not include IDE info in
.js
files at all, instead let IDEs (and other tools) load this data lazily - probably not by themselves, but using some IDE-helper code for that in Amber itself.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.