feat: fix live reload

[zugdev]

Resolves #358

[github-actions]

Unused devDependencies (1)

Filename	devDependencies
package.json	nodemon

[ubiquity-os-deployer]

9949639

05a81b1

abd8486

462c0dd

398f0df

9819021

7dc6d63

[github-actions]

Preview Deployment
7dc6d634506640ee2d0d935ab3781db7e8cfdf76

[EresDev]

• Unit tests are failing here. They need your attention.

• npm-run-all should be in dev dependencies.

• Would be nice if watch can also do a little Timestamp: Build started..., Timestamp: Build finished... message to give feedback on console too. Currently it just stays silent on rebuild.

[ubiquity-os]

@zugdev, this task has been idle for a while. Please provide an update.

[zugdev]

• Unit tests are failing here. They need your attention.

Tests are failing in development branch. I've looked into it and it doesn't seem to be induced by the presented changes. @EresDev please let me know if you think it is. Else, we should create another issue to look at it.

[EresDev]

Tests are failing in development branch.

Unit tests are not failing in development branch. They are passing there.

[zugdev]

@EresDev pardon, you are correct. Do you have any idea why it fails? I can't run these tests locally, and the changes seem very harmless. They might be a problem if under the hood the tests rely on yarn start or similar.

[EresDev]

Do you have any idea why it fails?

Tests are passing for me either I keep or remove nodemon. The problem can be the yarn.lock. You should try with yarn.lock file from the development branch.

[zugdev]

If the problem is in yarn.lock then some package should be added to package.json. I have no means of using "development" yarn.lock, I will commit it here but I am not able to run tests locally because the yarn.lock does not reflect my installed packages.

[EresDev]

Unit tests are passing. Now run the yarn install and commit the updated yarn.lock. You also have other points to look into.

[zugdev]

Unit tests are passing. Now run the yarn install and commit the updated yarn.lock.

That won't work.

You also have other points to look into.

The esbuild API has a build info option but IMO it's not useful and adds text overhead. I will enable it, tho.

[EresDev]

That won't work.

I tried that. It was working for me.