samjt
samjt
Sure, I thought that would be the case but I don’t think I can open a pr to start a new repo. Feel free to close
Sure, that makes more sense, I guess I should describe the solution more as a workaround for the time being.
I think this might also fix https://github.com/parcel-bundler/parcel/pull/7626 because the transform to commonjs probably shouldn’t be happening? Or maybe that’s specific to the svg use case
I've updated to devdep and it's passing now
Amazing, and great detailed documentation, thank you.
Sure, the idea was more that in a monorepo where each new figma plugin is a new workspace, this would enable creating them directly more easily, rather than wrapping create-figma-plugin...
Yes, the idea was that this would make using create-figma-plugin in a monorepo easier as monorepo workspaces require a name in the package json
@rahul-thakoor Sorry for the direct ping, I'm not sure if this repo is still actively maintained or not, or just dependency maintenance?
One point to note: async imports are treated as esm based on the dependency specifiertype returned to the resolver.
@devongovett It came from attempting to build an SVG library that exported as pure esm. When using the glob resolver to do this I would get back an objects rather...