You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Or at least to stop watching the locales dir? Calling .configure on the i18n instance once more with autoReload: false doesn't do anything. No wonder. After watching is started it just stays.
In my case I write unit tests for my platform, which utilizes i18n and sets autoReload to (NODE_ENV ==="development"). So when I run the tests it works fine, but when I develop them... After tests are done I do an automatic cleanup, which means the locales dir needs to be purged. But instead I get an exception. Because the dir continues to being watched even after I seemingly destroy my platform.
Please introduce a destructor, that unwatches the dir and/or let watching/unwatching procedure run on every .configure call.
Thanks
The text was updated successfully, but these errors were encountered:
Or at least to stop watching the locales dir? Calling
.configure
on the i18n instance once more withautoReload: false
doesn't do anything. No wonder. After watching is started it just stays.In my case I write unit tests for my platform, which utilizes i18n and sets
autoReload
to(NODE_ENV ==="development")
. So when I run the tests it works fine, but when I develop them... After tests are done I do an automatic cleanup, which means the locales dir needs to be purged. But instead I get an exception. Because the dir continues to being watched even after I seemingly destroy my platform.Please introduce a destructor, that unwatches the dir and/or let watching/unwatching procedure run on every
.configure
call.Thanks
The text was updated successfully, but these errors were encountered: