Skip to content
This repository was archived by the owner on Aug 22, 2022. It is now read-only.
This repository was archived by the owner on Aug 22, 2022. It is now read-only.

Pkger + fswatch issue #142

@AlexandreBernard

Description

@AlexandreBernard

I am using fswatch to live reload our go code on docker development machines using this principle :

https://levelup.gitconnected.com/how-to-live-reload-code-for-golang-and-docker-without-third-parties-ee90721ef641

fswatch -or --event=Updated ./my-project | xargs -n1 -I{} <cmd>

I'm trying to add Pkger to the process in order to trigger pkger before every re-compilation before live reload occurs

I've excluded pkged.go from fswatch watched files and only listens to Update events of course. But no matter what I do it ends up recompiling endlessly

I've also came to the conclusion that when I run the command manually it triggers two recompilations while the pkged output file is still ignored

Any idea why such thing is happening? Does Pkger touches some file meta information maybe? In any case that's not something I would expect

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions