fix: Acode ignoring main, readme and icon fields in plugin manifest

[alMukaafih]

Fix to Acode Ignoring main, readme and icon fields in plugin manifest (#1026)

[bajrangCoder]

It fails to load existing plugins

[alMukaafih]

It fails to load existing plugins

I will look into it

[bajrangCoder]

I think problem is in plugin templates , as it points to main: "dist/main.js" but in zip file it's not in dist folder .

So handle this as legacy one

[alMukaafih]

I think problem is in plugin templates , as it points to main: "dist/main.js" but in zip file it's not in dist folder .

So handle this as legacy one

I noticed this issue too. That is why I was testing for the existence of pluginJson.main before defaulting to "main.js" but it seems something went wrong somewhere.

[bajrangCoder]

The issue persists when loading previously published plugins; we need to implement a legacy solution to ensure compatibility.

[alMukaafih]

The issue persists when loading previously published plugins; we need to implement a legacy solution to ensure compatibility.

I tried it on a clean install and it works. On an update it fails to load previously installed plugins.

[bajrangCoder]

To maintain compatibility, you can implement a simple check during the plugin load process. If the main field is set to dist/main.js, treat it as main.js instead. That's the main cause for problems.

[alMukaafih]

To maintain compatibility, you can implement a simple check during the plugin load process. If the main field is set to dist/main.js, treat it as main.js instead. That's the main cause for problems.

I have implemented a more comprehensive check with my latest push. If the file that the main field points to does not exist, it falls back to the previous implementation of loading main.js .

[bajrangCoder]

Oo that's nice . But there are errors when listing local files in sidebar (I have tried your latest commit)