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 Aug 20, 2018. It is now read-only.
Hello, I have json files with the extension .schema that I am attempting to load in a webpack build. The relevant webpack configuration bits are as follows:
So, in a source file, when I import .json modules, there is no issue, but when I import a file with the .schema extension, it seems to be parsed by babel, instead, like follows:
OK, I figured out what is wrong, and it is quite embarrassing. LOL
I am running the server for dev mode directly from babel, not via the webpack build, so of bloody course these settings are not helping anything.
So, it brings me to a question...how would someone go about using this loader without webpack? Or is it possible to direct babel to see alternate extensions as json files?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, I have json files with the extension
.schema
that I am attempting to load in a webpack build. The relevant webpack configuration bits are as follows:So, in a source file, when I import
.json
modules, there is no issue, but when I import a file with the.schema
extension, it seems to be parsed by babel, instead, like follows:Any insights as to why this may be happening will be greatly appreciated.
The text was updated successfully, but these errors were encountered: