user-1
(User 1)
May 16, 2023, 12:26pm
#1
This topic was automatically generated from Slack. You can find the original thread here .
Hey, me and were are working on this task today and found a problem.
I thing action are not able to build the typescript, I’m experiencing the same problem on my computer (Windows with WSL2), but @U03BBH9F5TQ can build normally on they own computer (Mac).
When I build and try publish I received the error “component create api call responded with status: 500, body: {“error”:“unexpected error, please contact support@pipedream.com ”}”
PipedreamHQ:master
← PipedreamHQ:html-to-markdown
opened 04:55PM - 08 May 23 UTC
## WHAT
<!--
copilot:summary
-->
### <samp>🤖 Generated by Copilot at 1824e67<… /samp>
This pull request fixes a dependency issue and updates the convert-html-to-markdown action in the formatting component. It pins the `jsdom` version to 21.1.1 and uses consistent import syntax across the component files.
<!--
copilot:poem
-->
### <samp>🤖 Generated by Copilot at 1824e67</samp>
> _Oh we're the crew of the formatting ship, and we work with code and yarn_
> _We've pinned the `jsdom` to twenty-one, and we've raised the action barn_
> _Heave away, me hearties, heave away with me_
> _We've fixed the dependency issue, and we've made the markdown free_
## WHY
## HOW
<!--
copilot:walkthrough
-->
### <samp>🤖 Generated by Copilot at 1824e67</samp>
* Update jsdom dependency to 21.1.1 and use alias syntax to avoid conflict with other components ([link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-f4f2f342e06e5a19ae472aa65049405204b3f82a2142e6bff6010cab30c136b6L3-R3), [link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-f4f2f342e06e5a19ae472aa65049405204b3f82a2142e6bff6010cab30c136b6L10-R10), [link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-846687f3a83f906e5a9e53cc9486c91bb2d51f62c1505b5f1eef38f8379c47dbL22-R22), [link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-32824c984905bb02bc7ffcef96a77addd1f1602cff71a11fbbfdd7f53ee026bbL1376-R1376), [link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-32824c984905bb02bc7ffcef96a77addd1f1602cff71a11fbbfdd7f53ee026bbL1383-R1383))
* Remove unused omniconvert component from `pnpm-lock.yaml` file ([link](https://github.com/PipedreamHQ/pipedream/pull/6349/files?diff=unified&w=0#diff-32824c984905bb02bc7ffcef96a77addd1f1602cff71a11fbbfdd7f53ee026bbL2765-L2770))
Cc: @U02A06JPKEH @UMT4G7E5P
user-1
(User 1)
May 16, 2023, 12:26pm
#2
I was able to build it and in my comment I shared screenshots of the action working on pipedream’s UI
user-1
(User 1)
May 16, 2023, 12:26pm
#3
But for some reason, the github action says it’s not publishable
user-1
(User 1)
May 16, 2023, 12:26pm
#4
cc can you help troubleshoot?
user-1
(User 1)
May 16, 2023, 12:26pm
#6
re: building in windows: can you try deleting the dist
folder in components/formatting
and then build again? I got it working after that using windows like Alyson’s screenshot
re: why it fails in GH actions – still checking
user-1
(User 1)
May 16, 2023, 12:26pm
#7
Yeah, I tried and don’t worked
user-1
(User 1)
May 16, 2023, 12:26pm
#8
I believe that, if we merge it should work despite what github action says
user-1
(User 1)
May 16, 2023, 12:26pm
#9
Not sure what will happen, but I think we can try!
user-1
(User 1)
May 16, 2023, 12:26pm
#10
it may not work, future PRs may fail in GH actions because of this merge and we will have to fix the github action
user-1
(User 1)
May 16, 2023, 12:26pm
#11
I don’t think it will affect future PRs because only the changed files in the PR are verified
user-1
(User 1)
May 16, 2023, 12:26pm
#12
Only if the PR changes a component in formatting