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

Why isn't there a packaging configuration file #958

Open
2 tasks done
iomjympq99190 opened this issue Apr 25, 2024 · 1 comment
Open
2 tasks done

Why isn't there a packaging configuration file #958

iomjympq99190 opened this issue Apr 25, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@iomjympq99190
Copy link

What is the example you wish to see?

When I have over 10 content files, only the ones that have been packaged are very large. Why isn't there a packaging configuration file that extracts public libraries into global variables and reuses them

Is there any context that might help us understand?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I checked the current issues for duplicate problems.
@iomjympq99190 iomjympq99190 added the documentation Improvements or additions to documentation label Apr 25, 2024
@aiktb
Copy link

aiktb commented May 25, 2024

The global context of each content script is independent and it is not possible to access functions across contexts.

This is determined by the extension architecture and has nothing to do with plasmo, which the Chrome Extension Document calls isolated worlds.

So if you have 10 content scripts, and all 10 content scripts reference the same library, plasmo must bundle that library in every generated content script.

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

No branches or pull requests

2 participants