[RFC] use `import.meta.url` or `import 'url:./xxx'` throw "Could not resolve bundle with id" and solution - Githubissues

PlasmoHQ / plasmo

🧩 The Browser Extension Framework

https://www.plasmo.com

MIT License

10.16k stars 352 forks source link

[RFC] use `import.meta.url` or `import 'url:./xxx'` throw "Could not resolve bundle with id" and solution #749

Open apades opened 1 year ago

apades commented 1 year ago

How do you envision this feature/change to look/work like?

It have some diff in dev and build when i use import style from 'url:./xxx.less', it will throw "Could not resolve bundle with id xxx"

What is the purpose of this change/feature? Why?

nothing

(OPTIONAL) Example implementations

it looks like parcel put all special import to a separate js.

if i add second js to manifest.json content_scripts, it will work.

(OPTIONAL) Contribution

[ ] I would like to contribute to this RFC via a PR

Verify canary release

[X] I verified that the issue exists in plasmo canary release

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.