-
Notifications
You must be signed in to change notification settings - Fork 174
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
Not emitting es modules #8
Comments
Thanks @jtmthf, this looks like a bug. I'll work on this today. |
fixed in 1.4.1. Demo: test.js export const A = 'this should show up';
export const B = 'this should never wind up in the bundle'; app.js import React from 'react';
import { A } from './test';
export default () => (
<div>
{A}
</div>
); Resulting
|
Very useful project here. One concern I had is that in
kit/webpack/browser.js
,modules
is not set tofalse
which means by defaultimport
statements are transpiled tocommonjs
meaning that not all tree shaking optimizations can be taken advantage of. However when I change this, there is no change in size of the output bundle. Not sure exactly why this is, and was wondering if you had an idea.The text was updated successfully, but these errors were encountered: