-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Using devtools with react-stylegudist #456
Comments
For The only thing I’m not sure about is the production build: should we disable sourcemaps in this case? |
So I should go with optional disabling ignoring or I can just remove devtools from ignored keys list? |
@n1313 Did you want to be able to change |
Hmmm, no, I don't think devtools matters for what I do.
…Sent from my iPhone
On 30 May 2017, at 19:12, Artem Sapegin ***@***.***> wrote:
@n1313 Did you want to be able to change devtools? What should we do for production build?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Yeah, typical... "People with numbers in their nicknames, they're all the same" :(((
…
|
I think it should explicitly disable |
The `devtool` setting in your webpack config will now get passed through for non-production environments, e.g., running the hot-reloading server. It will still get ignored for production builds. Docs updated, and added a test.
Hi,
I know that
devtools
are ignored along with some other configuration keys.My question is:
react-stylegudist
entirely or there are some edge cases?Thanks for your time!
The text was updated successfully, but these errors were encountered: