-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fix source map #211
Fix source map #211
Conversation
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## develop #211 +/- ##
===========================================
+ Coverage 19.34% 19.53% +0.18%
===========================================
Files 16 15 -1
Lines 1070 1065 -5
Branches 371 373 +2
===========================================
+ Hits 207 208 +1
+ Misses 840 834 -6
Partials 23 23 see 7 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. The little bit of size should be ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one, I'm just not sure about including the typechain types, is this necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a341b73
to
e3c60b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should maybe think about removing the Typechain Types which are not used in the code, as I know there are a lot generated which are not relevant to export
What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
This PR introduce source map.
What is the current behaviour (you can also link to an open issue here)?
When on a dapp an issue comes from the lsp-factory library, it s not possible to have a look at the typescript file of the library.
What is the new behaviour (if this is a feature change)?
We can access the typescript file of the library from the browser of the dapp.
Other information:
It was a real concern for me that activating inline source map increases the weight of the library
(From 990kB to 1.2 MB) as we want our library to be as light as possible.
On this topic Andrea said that
"There is currently really no other way. Normally the consumer of the library should just be able to work with the source code if we had a real language".