jason0x43 on master
chore: update webdriver versions Update webdriver versions (compare)
jason0x43 on gh-pages
Update assets (compare)
jason0x43 on 2.3.3
jason0x43 on 2.3
Updating metadata for 2.3.3 Updating source version to 2.3.… (compare)
jason0x43 on 2.3
More mouseMoveTo updates Relax… (compare)
jason0x43 on 2.3
Update mouseMoveTo test to work… (compare)
jason0x43 on 2.3
Backport fix parent frame switc… Backport fix capabilities for S… Backport webdriver fixes for IE… and 6 more (compare)
dependabot[bot] on npm_and_yarn
jason0x43 on master
Bump highlight.js from 9.15.8 t… (compare)
{
"compilerOptions": {
"noImplicitAny": true,
"noImplicitUseStrict": true,
"noEmitOnError": false,
"module": "amd",
"moduleResolution": "classic",
"target": "es5",
"sourceMap": true,
"experimentalDecorators": true,
"types": ["intern"],
"baseUrl": ".",
"paths": {
"abc/*": ["src/abc/*"],
"def/*": ["src/def/*"]
}
},
"exclude": [
"node_modules"
],
"include": [
"src/**/*",
"tests/unit/**/*"
],
"files": [
"./node_modules/dojo-typings/dojo/1.11/index.d.ts",
"./node_modules/dojo-typings/dojo/1.11/modules.d.ts",
"./node_modules/dojo-typings/dijit/1.11/index.d.ts",
"./node_modules/dojo-typings/dijit/1.11/modules.d.ts",
"./node_modules/dojo-typings/dojox/1.11/index.d.ts",
"./node_modules/dojo-typings/dojox/1.11/modules.d.ts",
"./node_modules/dojo-typings/dojox/1.11/html/entities.d.ts",
"./node_modules/dojo-typings/custom/dgrid/1.1/dgrid.d.ts",
"./node_modules/dojo-typings/custom/dstore/1.1/dstore.d.ts"
]
}
You may be able to use paths
, like
{
"compilerOptions": {
"paths": {
"@theintern/common": ["node_modules/@theintern/common/index"],
"source-map": ["node_modules/source-map/source-map"]
}
}
However, you may still run into issues because modules published through npm are going to assume node-based module resolution.
Funny, someone else just pinged me because GHA recently updated to Chrome 83 and their tests started failing. :grinning: Intern's policy is to track the current stable versions of webdrivers by default. If you need to pin to a specific driver version, you can do that using tunnelOptions.drivers
:
{
"tunnelOptions": {
"drivers": [
{ "name": "chrome", "version": "81..." }
]
}
}
We can actually make that a bit easier with GHA, because (at least according to their release notes) they publish something to a CHROMEWEBDRIVER
environment variable in the container. I haven't checked to see what that contains, though (path to an exe, version number, ...).
This version of ChromeDriver only supports Chrome version 83
INTERN_ARGS
environment variable to pass command line options, but it's not very ergonomic for something like this.
Timeout: [POST http://localhost:4444/wd/hub/session / {"desiredCapabilities":{"name":"intern","idle-timeout":60,"browserName":"firefox","moz:firefoxOptions":{"args":["-headless"],"browser":"firefox"}}] connection refused
require.undef
) to force-load it (without mocked dependencies) the next time it is needed.