-
Notifications
You must be signed in to change notification settings - Fork 94
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
Allow exports in export
block
#554
Comments
Valid request. We would need to add It's a different case from other ExportedNamedDeclarations. Should be fairly straightforward if you want to open a PR. |
Would it be (easily) possible to also support var storyDefault = {
title: "Custom Title"
};
export {
hello_world ,
storyDefault as default,
} If this is not yet covered by #556, would anybody have some pointers on what needs to be done to support it? |
@woeps have you tried my branch? There's a test you can probably modify and see if it works already |
@i-am-the-slime I tried your branch locally and it seems |
@woeps I mean this one on my fork/branch:
|
Is your feature request related to a problem? Please describe.
I'm using ladle with PureScript and it almost works. It's just that the compiler output looks like this:
This leads to the following error:
If I manually change this to say
export var someStory =...
and remove theexport
block it works fine.Interestingly, it keeps working from there on out (so even when the file gets overwritten)
Describe the solution you'd like
I'd love for this to simply work without me having to change the output of the compiler.
Describe alternatives you've considered
If there was a way to hook into the reading of files, I could probably fix this with some regex or something more bespoke that traverses the AST, so that could be an alternative.
If that's something I could do with vite out of the box I'd be happy about any pointers.
The text was updated successfully, but these errors were encountered: