Closed
Bug 1644755
Opened 6 years ago
Closed 3 years ago
[meta] Upgrade pretty-fast for each release, if needed
Categories
(DevTools :: Debugger, enhancement, P2)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: jlast, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
Github has plenty of changes that we should have in Firefox. And in general the two should remain in sync
Comment 1•5 years ago
|
||
Should happen at the beginning of the cycle (to reduce risk).
Honza
Severity: -- → S3
Priority: -- → P2
Comment 2•5 years ago
|
||
On the github repo, I guess we should check if there was any significant commit made in the repo since the last release, and if so, bump the version number, do a release, and publish it to npm.
Then, from devtools side, this should be fairly easy:
cd devtools/client/debuggernpm outdated pretty-fast, if something is printed, thennpm update pretty-fastnode bin/bundle
This would update devtools/client/debugger/src/workers/pretty-print/worker.js, and then we can check on try if everything is still okay.
Keywords: meta
Summary: Upgrade pretty-fast → [META] Upgrade pretty-fast for each release, if needed
Updated•5 years ago
|
Summary: [META] Upgrade pretty-fast for each release, if needed → [meta] Upgrade pretty-fast for each release, if needed
Comment 3•3 years ago
|
||
this won't be needed anymore with Bug 1803360
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•