npm run build doesn't create valid chrome extension.

[TheRealJamesRussell]

After running npm run build the chrome-extension file, when loaded into chrome says there's no valid manifest file.

I looked into what up:

Seems like it names it weirdly (and includes the firefox manifest?)

Anyways, I renamed to just "manifest.json" and deleted firefox. that fixed it.

[TheRealJamesRussell]

I see you added into the package.json to rename the file just to manifest.json but it doesn't seem to do that.

[AkashKarnatak]

When you run npm run build, a new folder called chrome-extension will be created. You have to load the extension from chrome-extension folder instead of extension folder.

[TheRealJamesRussell]

The screenshot above is from the chrome extension file.

On Tue, 30 Jan 2024, 22:50 AkashKarnatak, @.***> wrote:

When you run npm run build, a new folder called chrome-extension will be created. You have to load the extension from chrome-extension folder instead of extension folder.

— Reply to this email directly, view it on GitHub https://github.com/AkashKarnatak/chatgpt-anywhere/issues/6#issuecomment-1917869795, or unsubscribe https://github.com/notifications/unsubscribe-auth/BCT5EJTBV53BT5JXAZOSEV3YRFMIDAVCNFSM6AAAAABCR3QWOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJXHA3DSNZZGU . You are receiving this because you authored the thread.Message ID: @.***>

[AkashKarnatak]

Seems like * wildcard character doesn't work as intended on windows. I'll look into it and get back to you.

[AkashKarnatak]

ed852f4d6fd30b5cf8dd1640663562cfb78ba462 fixes the issue