web_accessible_resources resources are not compiled if they are typescript files

[woss]

Following code snippet is the part of the manifest setting

  "content_scripts": [
    {
      "js": [
        "src/content.ts"
      ],
      "matches": [
        "http://*/*",
        "https://*/*"
      ],
      "run_at": "document_start"
    }
  ],
 "web_accessible_resources": [
    {
      "resources": [
        "src/myPageToInject.ts"
      ],
      "matches": [
        "http://*/*",
        "https://*/*"
      ],
      "use_dynamic_url": true
    }
  ],

Yields something like this:

  "web_accessible_resources": [
    {
      "matches": [
        "http://*/*",
        "https://*/*"
      ],
      "resources": [
        "src/myPageToInject.ts",
        "assets/content.ts-b571cc48.js"
      ],
      "use_dynamic_url": true
    }
  ],

The in the dist is still unprocessed TS file. Is this a bug or a missing feature?

[insilications]

It would be nice to have this feature.

[woss]

i agree, i was going through the code and indeed there is no compilation process for the web-accessible-resources

@jacksteamdev how hard would this be to implement?

[YunFeng0817]

@jacksteamdev I also really want this feature. Is there any plan to support this in the future?

[flexchar]

This repo is probably dead... :(

[woss]

i wonder is he alive? also i wonder why creators of popular repos don't write something about the lack of their time so others can contribute or at least know not to use the project since it might not receive updates or new features.

[flexchar]

I'm a developer myself. Sometimes the life aligns in such a way that the next weekend where I thought I'm gonna sit down and contribute never arrives. Open Source also doesn't pay the bills as easily (although I'm more than open supporting the painful work it does and abstracts from us). I do agree on the lack of communication. It feels like the current README preaches as this being the ultimate winner but the commit history hits below the waist.

Last night I found this. Looks very promising but a whole new thing to learn. I wish the core team working on the Manifest 3 had considered developers and HMR feature for local development. If not reloading, many of us would probably stick to existing tools. :)

https://www.plasmo.com
https://github.com/PlasmoHQ/plasmo

[woss]

unfortunately, the OSS doesn't pay the bills for 98% of the OSS creators. I started a project some time ago that might have changed that but it didn't took off, yet.

do you mind telling me why did you consider moving from plasma(if you are using it) to this?

i could use some alternatives :)

[flexchar]

I actually moved FROM ParcelJS to this to get proper HMR working on content scripts. But now I need a script in the MAIN world and this doesn't support. So I am considering moving TO Plasma as it seems to support everything one can imagine (looking at their examples repo here).

They're also a commercial product and 30usd/mon is more than fine if it saves me a couple of hours and lowers mental complexity! But I have not tried yet.

[woss]

thanks for the info, i will keep this in mind :)

[beautyfree]

Same needs

[flexchar]

I keep getting notifications... I wanted to say I moved to Plasmo framework. It works wonders. It doesn't have proper HMR for Vue but it allows to do so much more already. I would definitely advise to give a shot if the code base is not big yet.

[MindsightsAI]

ANy updates on this? How to solve that problem? Maybe anybody know workarounds?

[jan-wilhelm]

From my experience I haven’t found any work around and simply resorted to writing web accessible resources in plain JavaScript

[b5414]

Instead of web_ass, you can do a trick with the module background + scripting.executeScript