-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Building with 3.0.2 fails on Windows if there's a build-figma-plugin.ui.cjs
file in the repo
#205
Comments
I don’t have a Windows machine so I can’t properly debug this. Would the fix be to specify |
No, that was just something I happened to need to add for a library I'm working on. The issue is having any config file at all on Windows. Having a config worked in 2.6.1, but failed when I updated. I haven't investigated, but based on this comment, something may have been fixed previously: #77 (comment) |
Just to confirm, the contents of the |
I have the same problem here on a Windows machine. The content of the config file does not matter. There seems to be a problem with resolving the path on Windows. |
Anything we can do to help fix this? I was just thinking about trying to add some values via a |
@fwextensions @janweigel – Happy to review and merge a PR if any of you would like to work on a fix! From the error message you shared, my suspicion is that the absolute path returned by create-figma-plugin/packages/build/src/utilities/build-bundles-async/build-bundles-async.ts Line 51 in d8238d3
Is the fix here to add a |
Same problem here (Windows 10):
|
i'm having the same issue here on Windows 11. i'm blocked... any ideas how to fix this?
|
I think this is #77 all over again. The
build-figma-plugin.ui.cjs
file is just this:When it's in the main directory,
npm run build
fails with this error:When the config file is removed, the build works, but the plugin doesn't, because it needs to pass
keepNames: true
to esbuild. (As an aside, it would be nice if this sort of config, as well as the manifest, could be passed on the command line, which would then avoid this problem.)The text was updated successfully, but these errors were encountered: