Skip to content

css-modules failed when using latest version. #166

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

Closed
fwh1990 opened this issue Apr 15, 2019 · 9 comments
Closed

css-modules failed when using latest version. #166

fwh1990 opened this issue Apr 15, 2019 · 9 comments

Comments

@fwh1990
Copy link

fwh1990 commented Apr 15, 2019

I am using scss + css-modules, but I can't hot reload the changes of scss files since I upgrade version from 4.3.0 to 4.3.1.

I have to downgrade to 4.3.0 now.

What happened? Any idea?

@cloudychen
Copy link

me too

@fwh1990 fwh1990 changed the title css-modules failed by using latest version. css-modules failed when using latest version. Apr 15, 2019
@ScriptedAlchemy
Copy link
Collaborator

Likely from this commit: 0ce2460

Send me a demo repo and ill have a look

@fwh1990
Copy link
Author

fwh1990 commented Apr 16, 2019

I debug source code, and find out something may cause error:

function updateCss(el, url) {

  ...

  if (!isUrlRequest(url)) {
    return;
  }

  ...

}

The url like http://localhost:8000/main.css, so !isUrlRequest(url) return true

@fwh1990
Copy link
Author

fwh1990 commented Apr 18, 2019

Would you fix this bug at your earliest convenience? I mean, don't use el.href, it will return absolute url.

@ScriptedAlchemy
Copy link
Collaborator

@fwh1990 open a pull request and ill review it. you know what you need better than me

@ScriptedAlchemy
Copy link
Collaborator

use the reloadAll command/option?

@cloudychen
Copy link

use the reloadAll command/option?

yes

@silvenon
Copy link

@fwh1990 it would be so great if you could send the PR 😁🙏

@fwh1990
Copy link
Author

fwh1990 commented May 20, 2019

I have tested every version from 4.3.0~4.5.1, and find out that the bug was fixed by PR-173.

Everybody can upgrade to version 4.5.1, thanks.

So, I can close this issue now.

@fwh1990 fwh1990 closed this as completed May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants