You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be similar to #99. I'm using pikapkg/web (as suggested in Polymer's project issue) to enable native imports which are required for Electron app. After few days I made my project to work but now I see bunch of errors when using marked element. So the Pika web transforms marked library and marked object has only default property and this property has package export.
Now I am not sure how to deal with this issue as Pica does not have "exclude" option to not transform it as ES module. Maybe we could use some type check when constructing the instance of marked renderer?
The text was updated successfully, but these errors were encountered:
@jarrodek You should be able to use the whitelist property on @pikapkg/web to skip the transformation of marked. Check out this comment. FredKSchott/snowpack#40 (comment)
I tried it but no luck. It still gets transformed.
As a walkaround I am calling a script on postinstall script to replace marked.Renderer with marked.default.Renderer and later marked() with marked.default().
Description
This may be similar to #99. I'm using
pikapkg/web
(as suggested in Polymer's project issue) to enable native imports which are required for Electron app. After few days I made my project to work but now I see bunch of errors when using marked element. So the Pika web transforms marked library andmarked
object has onlydefault
property and this property has package export.Now I am not sure how to deal with this issue as Pica does not have "exclude" option to not transform it as ES module. Maybe we could use some type check when constructing the instance of marked renderer?
The text was updated successfully, but these errors were encountered: