yarn build failing on fork of repo
See original GitHub issueWhat package(s) are you using?
-
carbon-components
Summary
yarn build spits out the following error after cloning and running yarn install on a fork of the monorepo.
Is there a step that I am missing in the setup of the monorepo?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Ask Question - Stack Overflow
Sure, running yarn install when you specify your own fork as the repository version, i.e. '"some-package": "mygitusername/some-package#my-branch ...
Read more >Use Azure Pipelines to build and publish a Node.js package
Build, deploy, and test JavaScript and Node.js apps with Azure Pipelines. ... 1 - Fork the sample code; 2 - Create your pipeline;...
Read more >Install from Source - Docs - Ghost
First you'll need to make a fork of the Ghost repository. ... Builds admin files on start & then watches for changes yarn...
Read more >Yarn install support for modules referenced as file
When running in pipelines, the installation with the Yarn completes successfully, but running tests of the app fails as it cannot find that ......
Read more >Build a Node.js and React app with npm - Jenkins
Fork and clone the sample repository; Create your Pipeline project in Jenkins; Create your initial Pipeline as a Jenkinsfile; Add a test stage...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey all! 👋 We’ve just recently merged in more support for building on Windows, I believe it will help to address this so definitely give it a shot! If not, feel free to comment again and I can re-open this!
@emyarod I was able to check out the fixes and I am getting the same behavior. I took a look in icons-angular for any places where .replace was used but did not find any. My guess is that it might have something to do with how the paths are written in
fs.writeFile(
. Not 100% sure though.