We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This will be very convenient to migrate off the webpack's raw-loader for specific file types, which always return a default export from them.
raw-loader
import { plainText } from 'some-file';
import plainText from 'some-file';
The text was updated successfully, but these errors were encountered:
IMO default exporting is a bad practice in most scenarios and often causes wired problems. I vote for keeping using named exporting.
default exporting
named exporting
Sorry, something went wrong.
The latest release 1.4.0 supported configuring the export ways. For your demand try passing the { namedExport: false }.
{ namedExport: false }
No branches or pull requests
This will be very convenient to migrate off the webpack's
raw-loader
for specific file types, which always return a default export from them.Before
After
The text was updated successfully, but these errors were encountered: