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
{{ message }}
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.
It'd be useful to have more contextual information available when rigging up the runtime.
The immediate use-case I can see is denoting that interface modules are stateless. Eg: when importing a CSS file, image, etc, the dev runtime should know ahead of time that it can replace them when appropriate. This would enable us to stop injecting module.hot.accept() and remove the tight-coupling to babel's ES -> CommonJS flags.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It'd be useful to have more contextual information available when rigging up the runtime.
The immediate use-case I can see is denoting that interface modules are stateless. Eg: when importing a CSS file, image, etc, the dev runtime should know ahead of time that it can replace them when appropriate. This would enable us to stop injecting
module.hot.accept()
and remove the tight-coupling to babel's ES -> CommonJS flags.The text was updated successfully, but these errors were encountered: