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.

Sign up for GitHub

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

Jump to bottom

emit assets with unknown info #3701

Closed
faga295 opened this issue Jul 4, 2023 · 5 comments
Closed

emit assets with unknown info #3701

faga295 opened this issue Jul 4, 2023 · 5 comments
Labels
bug Something isn't working stale

Comments

@faga295
Copy link
Contributor

faga295 commented Jul 4, 2023 •
edited
Loading

System Info

System:
OS: macOS 13.0
CPU: (8) arm64 Apple M1 Pro
Memory: 56.33 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
Yarn: 1.22.15 - ~/.nvm/versions/node/v16.14.2/bin/yarn
npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
pnpm: 6.11.0 - ~/.nvm/versions/node/v16.14.2/bin/pnpm
Browsers:
Chrome: 114.0.5735.198
Safari: 16.1
npmPackages:
@rspack/cli: 0.2.4 => 0.2.4

Details

When emit assets with unknown info, it doesn't work.
In this example, I emit asset with { compressed: true }, but it doesn't appear in stats
rspack:
image
webpack:
image

I'm currently working on #3677 this pr, but blocked by this bug

Reproduce link

https://github.com/faga295/rspack-reproduce/tree/emit_assets_with_unknown_info

Reproduce Steps

  1. pnpm run build:rspack
  2. pnpm run build:webpack
  3. compare the difference of output
@faga295 faga295 added bug Something isn't working pending triage The issue/PR is currently untouched. labels Jul 4, 2023
@faga295 faga295 changed the title fix: emit assets with unknown info emit assets with unknown info Jul 4, 2023
@hyf0 hyf0 removed the pending triage The issue/PR is currently untouched. label Jul 6, 2023
@hyf0 hyf0 added this to the Planned milestone Jul 6, 2023
@suica suica mentioned this issue Jul 25, 2023
Closed
11 tasks
@faga295 faga295 mentioned this issue Jul 26, 2023
Closed
@stale
Copy link

stale bot commented Sep 4, 2023

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@stale stale bot added the stale label Sep 4, 2023
@hardfist hardfist removed this from the Planned milestone Oct 6, 2023
@stale stale bot removed the stale label Oct 6, 2023
@stale Stale
Copy link

stale bot commented Dec 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@stale stale bot added the stale label Dec 5, 2023
@faga295
Copy link
Contributor Author

faga295 commented Dec 5, 2023

bump

@stale stale bot removed the stale label Dec 5, 2023
@stale Stale
Copy link

stale bot commented Feb 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@stale stale bot added the stale label Feb 3, 2024
@LingyuCoder
Copy link
Collaborator

StatsAsset.info has been aligned by #6951. I will close this issue, and if you encounter new problems, you can just reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@LingyuCoder @hardfist @hyf0 @faga295