Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content file does not execute #176

Open
hg2990656 opened this issue May 24, 2023 · 8 comments
Open

Content file does not execute #176

hg2990656 opened this issue May 24, 2023 · 8 comments

Comments

@hg2990656
Copy link

I clone the latest project and run the code and add it to chrome extension, but it didn't print the log in index.js of Content.

@tibic
Copy link

tibic commented Jun 15, 2023

i have the same problem

@KirillSuhodolov
Copy link

the same

@nzayatz14
Copy link

nzayatz14 commented Jun 20, 2023

I also, and Im getting errors when loading the dev pages
Screenshot 2023-06-20 at 1 38 00 PM

@aldrinjenson
Copy link

same issue. how to fix this?

@mszajner
Copy link

The problem is that the background and content scripts have hot-reload enabled. This causes them to want to connect to the server (which has a different origin and/or protocol). The way around it is to build a plugin to the build directory and manually update it in the browser from there.
For example, the workaround is just to remove ZipPlugin from utils/build (or make a copy), then run: npm run build and reload manually plugin in Chrome browser from build directory.

@minarainbow
Copy link

Was there a good fix for this?

@iqbalexperience
Copy link

Will there be any development on this issue in future?

@jasekt
Copy link

jasekt commented Sep 3, 2023

Solved in issue #150

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants