- Notifications
You must be signed in to change notification settings - Fork47
Broken build due to import#22
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
import statement which ends up appearing in the built parser. With the latest release of this module, this breaks my code sinceimport statements aren't directly supported. In general, this could be handled by preprocessing with something like Babel, but in this case, the import wasn't actually used so I just removed it.Please excuse the typo which caused the horribly long initial title. |
@michaelmior sorry for the typo. new version: v1.1.0 has released to fix this issue. It's probably caused by my typo when editing "travel". When I type "ti" in vscode, and it just add Will add test case to check these case before release. |
No problem. Thanks for the fix! |
Uh oh!
There was an error while loading.Please reload this page.
There is currently an unused
importstatement which ends up appearing in the built parser. With the latest release of this module, this breaks my code sinceimportstatements aren't directly supported. In general, this could be handled by preprocessing with something like Babel, but in this case, the import wasn't actually used so I just removed it.Would be great if another release could be made after this is merged :)`