You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running plasmo build --minify --source-maps produces
Also this command runs extremely slow compared to the first one - 10s vs 200s (logs below). The step which takes up all the time is 🟡 0 | @plasmohq/parcel-packager, the last one.
Docs state that building for prod doesn't produce source maps by default but apparently it does - however I don't see any sourcemaps in the first produced bundle. But I will be honest I'm not nearly skilled enough to dig through both minified files to determine where does the bloat come from. I think I've tried rebuilding with vanilla tsconfig & package.json from create plasmo and results were the same but perhaps I've missed something.
You're using an older version of plasmo - the newest will respect the minify flag. We remove minification by default due to chrome's production build requirement (they do not like obfuscated/bundled code)
What happened?
Running
plasmo build --minify
producesRunning
plasmo build --minify --source-maps
producesAlso this command runs extremely slow compared to the first one - 10s vs 200s (logs below). The step which takes up all the time is
🟡 0 | @plasmohq/parcel-packager
, the last one.Docs state that building for prod doesn't produce source maps by default but apparently it does - however I don't see any sourcemaps in the first produced bundle. But I will be honest I'm not nearly skilled enough to dig through both minified files to determine where does the bloat come from. I think I've tried rebuilding with vanilla tsconfig & package.json from
create plasmo
and results were the same but perhaps I've missed something.The repo is here
Version
Latest
What OS are you seeing the problem on?
Windows
What browsers are you seeing the problem on?
No response
Relevant log output
(OPTIONAL) Contact Details
ckuka71@gmail.com
Code of Conduct
The text was updated successfully, but these errors were encountered: