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

Live reloading not working on Ubuntu when there is no CSS file #342

Open
martiuh opened this issue Apr 27, 2019 · 3 comments
Open

Live reloading not working on Ubuntu when there is no CSS file #342

martiuh opened this issue Apr 27, 2019 · 3 comments

Comments

@martiuh
Copy link

martiuh commented Apr 27, 2019

So I started using charge today and I really like the idea of it.
The problem is that live reloading does not work out of the box, I think the issue is with browsersync because I installed reload and set it to listen to tmp/target directory and it was working well.

Here are some stats of my computer
System:
OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
CPU: (4) x64 AMD A8-6410 APU with AMD Radeon R5 Graphics
Memory: 2.58 GB / 14.64 GB
Container: Yes
Shell: 2.7.1 - /usr/bin/fish
Binaries:
Node: 8.11.4 - ~/.config/fnm/bin/node
Yarn: 1.12.3 - ~/.linuxbrew/bin/yarn
npm: 5.6.0 - ~/.config/fnm/bin/npm
Browsers:
Chrome: 73.0.3683.86
Firefox: 66.0.2

EDIT

So as soon as I added CSS I got the BrowserSync is active notification and did live reload.

@martiuh martiuh changed the title [BUG] Live reloading not working on Ubuntu [BUG] Live reloading not working on Ubuntu when there is no CSS Apr 27, 2019
@martiuh martiuh changed the title [BUG] Live reloading not working on Ubuntu when there is no CSS [BUG] Live reloading not working on Ubuntu when there is no CSS file Apr 27, 2019
@brandonweiss brandonweiss changed the title [BUG] Live reloading not working on Ubuntu when there is no CSS file Live reloading not working on Ubuntu when there is no CSS file Apr 27, 2019
@brandonweiss
Copy link
Owner

Thanks for the report!

Hmm. Yeah, that’s almost certainly an issue with brower-sync 😒 I haven’t been particularly happy with it as a library… it’s a bit difficult to use, the documentation is confusing, and it has… 423 open issues 🙀 But, it is the most popular library for live-reloading.

I hadn’t heard of reload. I’ll take a look at it and see if maybe it’s worth replacing brower-sync!

@thebergamo
Copy link
Contributor

@brandonweiss I also had some problems with live reloading specially for jsx files. I also got me thinking about use parcel to bundle everything. It also have same principle of zero-config.

If you think it makes sense, I can create a PR with that implementation. I believe it would make few things easier also.

Btw, I fall in love with charge :D You did a great work!

@brandonweiss
Copy link
Owner

@thebergamo Thanks so much! I’m glad you love it! ❤️

What are the issues you’re running into with reloading JSX files?

You mean using Parcel to bundle the JavaScript? Or… everything? I’m not totally sure what you’re proposing. My understanding of Parcel is that it’s a high-level application bundler, similar to Webpack. I think that would make Parcel sort of analogous to Charge, rather than something Charge could potentially use internally. But maybe I don’t understand Parcel well enough. Let me know what you were thinking!

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

No branches or pull requests

3 participants