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

Webpack loaders don't support .bmp - with PR #1033

Closed
bebbi opened this issue Nov 10, 2016 · 3 comments
Closed

Webpack loaders don't support .bmp - with PR #1033

bebbi opened this issue Nov 10, 2016 · 3 comments

Comments

@bebbi
Copy link
Contributor

bebbi commented Nov 10, 2016

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

yes, 3.10.9
If you're using OS X or Linux, run this to update npm:

Description

Can't import .bmp files without the PUBLIC_FOLDER workaround

Expected behavior

Compilation succeeded :-)

Actual behavior

Failed to compile.

Error in ./src/sonic.bmp
Module parse failed: /Users/me/fabric/src/sonic.bmp Unexpected character '�' (1:3)
You may need an appropriate loader to handle this file type.
SyntaxError: Unexpected character '�' (1:3)
@ ./src/MyStuff.js 16:13-35

I'll prepare a PR to add bmp to the webpack module loaders in prod and dev.

@gaearon
Copy link
Contributor

gaearon commented Nov 20, 2016

BMP is not a web image format. It's extremely heavy.
We should not be encouraging people to use it on the web.

Since there is a workaround (public folder) I would like to close this.
Sorry!

@gaearon gaearon closed this as completed Nov 20, 2016
@bebbi
Copy link
Contributor Author

bebbi commented Nov 20, 2016

This is solved via #667. Agree but still happy because the use-case requires 50 x 1.5k original bmps that I can now consider source of truth as-is and inline :)

On 20 Nov 2016, at 19:57, Dan Abramov notifications@github.com wrote:

BMP is not a web image format. It's extremely heavy.
We should not be encouraging people to use it on the web.

Since there is a workaround (public folder) I would like to close this.
Sorry!


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #1033 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ACn_h9Zd8oq5mxm-TcZg59hDeKrXmzURks5rAJgNgaJpZM4KvDTG.

@gaearon
Copy link
Contributor

gaearon commented Nov 20, 2016

Fair enough :-)

@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants