Closed
Bug 1478739
Opened 7 years ago
Closed 7 years ago
Non ES5 code in HCT lib is breaking uglify builds
Categories
(Toolkit :: Telemetry, enhancement, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: muffinresearch, Assigned: janerik)
Details
Attachments
(1 file)
Having submitted a PR for the implementation of HCT on the disco pane our bundle builds are breaking due to ES6 code in the lib.
Typically most packages publish ES code.
We can also look to update to uglify-es but this might slow down the implementation because it has other dependencies.
To make the HCT lib uglifyable you can simply:
* Remove arrow functions 52
* Remove object shorthands 37, 81, 85
Alternatively transpile the library as part of the build process.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jrediger
Priority: -- → P1
| Reporter | ||
Comment 1•7 years ago
|
||
This line:
Typically most packages publish ES code.
Should be:
Typically most packages publish ES5 code.
| Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment on attachment 8995962 [details]
Bug 1478739 - Don't use object shorthands and arrow functions in HCT.
Chris H-C :chutten has approved the revision.
https://phabricator.services.mozilla.com/D2508
Attachment #8995962 -
Flags: review+
Pushed by jrediger@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/802725c77093
Don't use object shorthands and arrow functions in HCT. r=chutten
| Assignee | ||
Comment 5•7 years ago
|
||
This is landing now. We will need to wait for :dexter to come back and push an NPM release (I'll make sure to get npm access afterwards for me and the team as well)
| Assignee | ||
Comment 6•7 years ago
|
||
I got access and published Version 1.1.1[1]
[1]: https://www.npmjs.com/package/mozilla-hybrid-content-telemetry
Comment 7•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•