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
Occasional error in morphdom-esm when saving changes #21
Comments
Until this gets some triage, just want to note that you can disable |
That is super helpful - thanks @zachleat! This is a great workaround for now! Sorry for not putting this in the right repo - I always assume things bundled with 11ty are in the main 11ty repo. |
(no worries at all!) |
I did make a slight modification to this code in 1.0.0-canary.8 of dev server, please retest after that release! |
|
Thanks @zachleat - I updated to 2.0.0-canary.5 and cannot get this to occur any longer. BTW - is there anywhere that lists what changes between canary/beta builds? I like to use the latest & greatest but its hard to tell what I am gaining by switching canary version unless I see a Tweet or you comment on a bug fix. Not really a complaint, just curious if a changelog existed that tracked this kind of thing :) |
@andy-bond the best way is to look at the Milestone (newest stuff is on top) https://github.com/11ty/eleventy/milestone/38?closed=1 Thanks! |
Describe the bug
I'm having trouble reproducing this, but this does occur fairly consistently in a project I'm working on when serving eleventy.
Essentially, I make some changes to a file and the elevent-dev-server tries to reload. It sometimes encounters the error below. If I save the file again, it will continue working normally.
I am running this via an Nx monorepo using the
@nrwl/workspace:run-commands
, so not sure if that affects anything. The equivalent command usingnpm-run-all
would be the command here.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ideally no error occurs and the changes are saved & page reloads
Environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: