Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have a node monorepo in the format of:
root:
-- index.ts
-- package.json
-- tsconfig.json
-- index.ts
-- package.json
-- tsconfig.json
-- myHelper.ts
-- package.json
-- tsconfig.json
And in my root's package.json
... "workspaces": [ "libraries", "project1", "project2" ], ...
This builds absolutely fine locally, and I can nav to ./project1 and build there as well.
When I try to run it in an Action, I can build at the root, and I can build the libraries folder, However when I try to build ./project1 inside of my github workflow, the action fails because of the error
error TS2307: Cannot find module 'libraries/myHelper' or its corresponding type declarations.
I'm currently testing locally on macos and the action is running ubuntu-latest, but I'm unsure why it doesn't work in the workflow when it succeeds locally. I even tried recloning my repo in a fresh directory and it builds fine there as well.
Is there special set ups inside of a Workflow such that Actions is aware of the workspace?
Beta Was this translation helpful? Give feedback.
All reactions