-
Notifications
You must be signed in to change notification settings - Fork 138
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
mjs build for cadence-parser #2851
Conversation
Cadence Benchstat comparisonThis branch with compared with the base branch onflow:master commit 45be606 Collapsed results for better readability
|
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.
beautiful
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2851 +/- ##
=======================================
Coverage 79.38% 79.38%
=======================================
Files 334 334
Lines 78826 78826
=======================================
Hits 62576 62576
Misses 13944 13944
Partials 2306 2306
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Thank you for looking into this and opening an alternative @nialexsan! How does it differ from #2815? What is wrong with approach in the existing PR and how is the approach in this PR better? (Not arguing in any way, just trying to understand) Could you please also follow and fill out the checklist in the template? Thanks! |
@turbolent this PR implements a generic approach for bundling and it uses a well known tool to do that
|
@nialexsan Thank you for the explanation! Agreed that it is preferable to have a single config 👍 |
alternative approach for #2815
Description
cadence-parser's build configuration is using tsc to build a dual package, however, the created esm module cannot be imported from a nodejs es module, as the "type": "module" is missing from the es module specific package.json.
This PR contains a way to solve this issue, although many other ways exist based on the choice of tooling. The solution included is an attempt to fix it with the smallest amount of change to the current toolings and configuration.
master
branchFiles changed
in the Github PR explorer