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

New post css files doesn't fire browser sync #1

Closed
TsvetomirElkin opened this issue Mar 27, 2018 · 5 comments
Closed

New post css files doesn't fire browser sync #1

TsvetomirElkin opened this issue Mar 27, 2018 · 5 comments
Assignees
Labels
good first issue Good for newcomers

Comments

@TsvetomirElkin
Copy link

When you add a new post css file you need to change already existing file and save it to fire browser sync and apply the new file styles.

@scriptex
Copy link
Owner

scriptex commented Mar 30, 2018

@TsvetomirElkin Do you mean scss file? Or maybe you are using the PostCSS branch? Please provide more details.

Edit: Now that i've had time to investigate, it appears that this is a known node-sass issue: sass/node-sass#1891 .

@scriptex scriptex added bug Something isn't working good first issue Good for newcomers and removed bug Something isn't working labels Mar 30, 2018
@TsvetomirElkin
Copy link
Author

TsvetomirElkin commented Apr 13, 2018

I use PostCSS branch. When I make new file, for example _header.css, the app.css doesn't update .I have to go back to some old .css file and save it, after that app.css get the new file _header.css. It's not a big deal, but I think it's good to note.

@scriptex
Copy link
Owner

scriptex commented Apr 15, 2018

Well, it looks like this is a common issue when working with glob CSS imports, regardless of the preprocessor used - postcss/postcss-cli#161

I will try to think of a solution when i have more time. This issue is also present in the master branch where I am using SASS along PostCSS.

@scriptex scriptex self-assigned this Apr 16, 2018
@scriptex
Copy link
Owner

scriptex commented Apr 18, 2018

This issue should be fixed in 4c29e8b. Can you please test it and let me know if it works for you? Just note that the fix is in the postcss branch :)

Update: The issue is now fixed in the master branch too: 3ba785e

@TsvetomirElkin
Copy link
Author

Yep, the issue is fixed.😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants