beenull/browsh
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
browsh/webext/package.json

32 lines
706 B
JSON
Raw Normal View History

First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
{
"scripts": {
First draft of integration tests
2018-01-23 04:28:56 +00:00
"get-gobindata": "go get -u gopkg.in/shuLhan/go-bindata.v3/...",
Launch and install webextension from client This means that Browsh can now be entirely run just by running the CLI binary. The client launches Firefox as a subprocess, then connects to it via the Marionette protocol, installs the webextension and finally triggers a new tab with, currently, the Google homepage in it. I was trying to set this up for automated testing as well by installing the built webextension as a temporary addon, because otherwise you need to sign the extension everytime with a unique semantic version. However for some reason I can't quite recreate the environment that MDN's `web-ext` creates. The extension installs fine but fails to load the `content.js` script, I can't find a backtrace or any other details about the failure. So for now, we're just going to have to use `web-ext` as seperate process and have the client connect to that. Which is what one should do during development anyway, so it's not a huge loss.
2018-01-21 03:56:05 +00:00
"build": "./contrib/bundle_webextension.sh",
Move integration tests to Golang CLI client After moving to Tcell and implementing its screen diff updates, we can no longer watch STDOUT to get frames during integration tests. Instead we need to use Tcell's SimulationScreen and which has a GetContents() method. This is actually also a much more robust way of being able to see what Browsh actually outputs during testing.
2018-02-17 05:52:03 +00:00
"test": "NODE_PATH=src:test mocha"
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
},
"babel": {
Refactored webext background script
2018-01-10 14:54:51 +00:00
"presets": [
"es2015"
]
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
},
"devDependencies": {
Refactored webext background script
2018-01-10 14:54:51 +00:00
"babel-eslint": "^8.1.2",
"babel-loader": "^7.1.2",
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
"babel-preset-es2015": "^6.24.1",
"babel-register": "^6.26.0",
"chai": "^4.1.2",
Launch and install webextension from client This means that Browsh can now be entirely run just by running the CLI binary. The client launches Firefox as a subprocess, then connects to it via the Marionette protocol, installs the webextension and finally triggers a new tab with, currently, the Google homepage in it. I was trying to set this up for automated testing as well by installing the built webextension as a temporary addon, because otherwise you need to sign the extension everytime with a unique semantic version. However for some reason I can't quite recreate the environment that MDN's `web-ext` creates. The extension installs fine but fails to load the `content.js` script, I can't find a backtrace or any other details about the failure. So for now, we're just going to have to use `web-ext` as seperate process and have the client connect to that. Which is what one should do during development anyway, so it's not a huge loss.
2018-01-21 03:56:05 +00:00
"copy-webpack-plugin": "^4.3.1",
Refactored webext background script
2018-01-10 14:54:51 +00:00
"eslint": "^4.15.0",
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
"mocha": "^4.1.0",
First draft of integration tests
2018-01-23 04:28:56 +00:00
"pty.js": "^0.3.1",
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
"sinon": "^4.1.3",
First draft of integration tests
2018-01-23 04:28:56 +00:00
"strip-ansi": "^4.0.0",
Launch and install webextension from client This means that Browsh can now be entirely run just by running the CLI binary. The client launches Firefox as a subprocess, then connects to it via the Marionette protocol, installs the webextension and finally triggers a new tab with, currently, the Google homepage in it. I was trying to set this up for automated testing as well by installing the built webextension as a temporary addon, because otherwise you need to sign the extension everytime with a unique semantic version. However for some reason I can't quite recreate the environment that MDN's `web-ext` creates. The extension installs fine but fails to load the `content.js` script, I can't find a backtrace or any other details about the failure. So for now, we're just going to have to use `web-ext` as seperate process and have the client connect to that. Which is what one should do during development anyway, so it's not a huge loss.
2018-01-21 03:56:05 +00:00
"web-ext": "^2.3.1",
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
"webpack": "^3.10.0"
},
"dependencies": {
First pass at supporting wide UTF8 chars like 中文
2018-01-14 14:25:38 +00:00
"lodash": "^4.17.4",
"string-width": "^2.1.1"
First draft of rewrite to Webextension and Rust This proves that frames can be generated on Firefox using the canvas and a Tree Walker to examine text nodes. Already with little optimisation frames don't ever take longer than 200ms to render. Chrome has a MediaStream of the viewport, hopefully that will prove performant as well. This doesn't have functioning text colour detection or text occlusion support. But early research suggests this will possible by comparing 2 screenshots: one with and the other without rendered text.
2017-12-30 13:37:28 +00:00
}
}
Reference in a new issue Copy permalink