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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing @parcel/transformer-typescript-types... fails when copy repo to another machine #7861
Comments
I'm running into the same issue on my local machine. Here's a working build on GitHub Actions: https://github.com/Zertz/react-headless-tabs/runs/5681490759 Locally (M1 Pro Mac), I'm getting different errors (for reasons unbeknownst to me!) in these terminals: VS Code (zsh)
Warp
This happens even after running I was about to publish a new version react-headless-tabs so you can use the main branch to try and reproduce the issue locally! |
Essentially a duplicate of #7515. The project root isn't determined correctly:
I'm not sure why a different machine or CI would change this. As a workaround, use Will be fixed by #7537 |
Just FYI, it worked fine as-is before 2.4.0 |
馃悰 bug report
I initially created a new project with
v2.3.2
, with Typescript, Storybook, Styled-components, the whole 9. The initial project setup went very smooth and I was up and running in about 30 minutes. However moving into a few weeks later to start working on my component library, I copied the repo locally to another machine, using the same versions ofnode
andnpm
. I rannpm install
,npm run build
and then not so happy.馃帥 Configuration
package.json
tsconfig.json
馃 Expected Behavior
To be able to have multiple people on different machines be able to copy repo from github and easily install dependencies, and build the library for local testing.
馃槸 Current Behavior
I did all of the suggestions, with no luck, I even tried updating to the latest release from a couple of days ago
v2.4.0
with no luck either.After the failed install my
package.json
file now looks like thisWhen I look in my
node_modules
folder all of the dependencies are there.馃拋 Possible Solution
Wish I had a solution but so far anything I can think of hasn't been plentiful.
馃敠 Context
Right now, this is really only affecting me as the project is just getting underway, however we may need to find an alternative resource to help with the component-library
馃捇 Code Sample
https://github.com/proper-px/component-library
馃實 Your Environment
The text was updated successfully, but these errors were encountered: