Janne Holm

Doesn't work out of the box in Windows. Seems to be a problem with directory handling (\ or double \ instead of /). I managed to get stuff working (serve...

This issue still persists in the new version, tested with NPM 6 and 8. The path created for require comes now as e.g /C:/GIT/project/systemjs-tools.js, which doesn't work in Windows. So...

For now it seems that if I change the following (**config.js line 26 and 30**): `configs.file = require(path.join('/', ...dir, 'systemjs-tools.js')).config` to `configs.file = require(path.join(...dir, 'systemjs-tools.js')).config` directory handling seems to work...

I created a fork with the aforementioned fixes https://github.com/jhholm/systemjs-tools You can try that if you want.

I tested with your config file, and I get the same error. I suppose the config file might be the issue. E.g. this should work. ``` var fs = require("fs");...

This would be excellent as we now have to use site designs + site scripts with a Sequence. It would also be helpful if a site design could be applied...

It seems that I got PnP JS Console successfully working in Firefox 108 with my hacky changes, but other functionalities seem to have small issues.

Small update. Got 6.6.0 popup working with Firefox. I had to change **chrome.runtime.executeScript** to use world: 'ISOLATED' instead of 'MAIN' as 'MAIN' is not yet supported in Firefox. The change...

* ISOLATED seems to work in both browsers, I did play around with a **isFirefox** approach initially * executeScript({ world: "main"... }).then((result) => fetch()) seems to work for some reason...

It seems that Chrome might have access to **scripting** and **tabs** in devtools.js, if permissions are set in manifest.json. At least console.logging them gives an object after proper permissions. Firefox...