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

[BUG] Override unstable #1143

Closed
abvdveen opened this issue Sep 29, 2020 · 4 comments · Fixed by #1322
Closed

[BUG] Override unstable #1143

abvdveen opened this issue Sep 29, 2020 · 4 comments · Fixed by #1322
Assignees
Labels
bug Something isn't working

Comments

@abvdveen
Copy link

Using shopware-pwa override copies the file, for instance /.shopware-pwa/source/components/SwFooter.vue correctly to /src/components/SwFooter.vue.

But when I then edit the latter, you'll always see a rebuild of the client and server in the shell running shopware-pwa dev, but the file in .shopware-pwa/source/components is not always updated. Most of the time it is replaced by an empty file, sometimes it gets updated. How can I debug the hot rebuild process to find the cause?

@abvdveen abvdveen added the bug Something isn't working label Sep 29, 2020
@niklaswolf
Copy link
Collaborator

I also see this behaviour, even if I only do some really small changes, for example adding a CSS class. When I refresh the site, I always get the following error: render function or template not defined in component. That's because the file in .shopware-pwa/source/components is empty as @abvdveen describes it.

@niklaswolf
Copy link
Collaborator

Maybe this has something to do with chokidar. https://github.com/DivanteLtd/shopware-pwa/blob/master/packages/nuxt-module/src/module.ts#L234
As I'm developing inside a docker container I recall many issues regarding chokidar not picking up file changes correctly when using volume mounts. The workaround for this apparently is to configure chokidar to use polling (CHOKIDAR_USEPOLLING=1 yarn dev). I'll try that and will report back.

@niklaswolf
Copy link
Collaborator

After some days using this workaround, I can say that it's MUCH more stable, in fact I did not have any errors while using it.

@abvdveen
Copy link
Author

@niklaswolf Thanks for the tip! Encountered the same error on the Hypernode platform and using CHOKIDAR_USEPOLLING=1 yarn dev seems to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants