[BUG] Unable to use compodoc with Apple Silicon M1 Chip
See original GitHub issueOverview of the issue
Unable to use compodoc
on M1 MacBook Pro. Not 100% sure if this relates to the Apple Silicon but as it seems to work on other Intel based MacBooks I assume it is.
Operating System, Node.js, npm, compodoc version(s)
- Operating System: macOs Monterey (12.1)
- Chip: Apple M1 Pro
- Node.js: 14.18.2
- npm: 6.14.15
- compodoc: 1.1.16
Angular configuration, a package.json
file in the root folder
{
"name": "ngx-storybook",
"private": true,
"version": "0.0.120",
"scripts": {
"start": "npm run storybook",
"prebuild": "rm -rf dist",
"build": "NODE_ENV=production build-storybook -o dist",
"build:watch": "exit 0",
"test": "exit 0",
"docs:json": "compodoc -p ./tsconfig.json -e json -d .",
"storybook": "npm run docs:json && start-storybook -p 6006"
},
"peerDependencies": {
"@angular/cdk": "13.x.x",
"@angular/common": "13.x.x",
"@angular/core": "13.x.x",
"@angular/forms": "13.x.x",
"@angular/platform-browser": "13.x.x",
"@angular/animations": "13.x.x",
"@angular/router": "13.x.x"
},
"dependencies": {
"tslib": "~2.1.0",
"zone.js": "~0.11.4"
},
"devDependencies": {
"@angular/animations": "~13.0.0",
"@angular/common": "~13.0.0",
"@angular/compiler": "~13.0.0",
"@angular/core": "~13.0.0",
"@angular/forms": "~13.0.0",
"@angular/router": "~13.0.0",
"@angular/platform-browser": "~13.0.0",
"@angular/platform-browser-dynamic": "~13.0.0",
"@angular-devkit/build-angular": "~13.0.0",
"@schiphol-ac/ngx-ac": "workspace:*",
"@angular/cli": "~13.0.0",
"@angular/compiler-cli": "~13.0.0",
"@angular/elements": "^13.0.2",
"@babel/core": "7.6.0",
"@compodoc/compodoc": "1.1.16",
"@storybook/addon-docs": "6.4.8",
"@storybook/addon-actions": "6.4.8",
"@storybook/addon-essentials": "6.4.8",
"@storybook/addon-links": "6.4.8",
"@storybook/angular": "6.4.8",
"@storybook/builder-webpack5": "^6.4.8",
"@storybook/manager-webpack5": "^6.4.8",
"@types/jasmine": "~3.10.0",
"@types/node": "14.17.3",
"@webcomponents/custom-elements": "^1.5.0",
"babel-loader": "8.2.3",
"typescript": "~4.4.4",
"@rushstack/heft": "0.41.7",
"@types/heft-jest": "~1.0.2",
"@types/jest": "~26.0.20",
"jest": "~26.6.3",
"ts-node-dev": "^1.1.8",
"ts-jest": "26.4.4",
"ng-packagr": "~13.0.0",
"rxjs": "6.5.5",
"tsconfig-paths-webpack-plugin": "~3.5.1"
}
}
Compodoc installed globally or locally ?
Locally
If possible your terminal logs before the error
Reproduce the error
Do the following on a Apple Silicon Chip:
compodoc -p ./tsconfig.json -e json -d .
Related issues
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[BUG] When npm i @compodoc/compodoc in M1 Mac #1050
This is Error comments npm ERR! command failed npm ERR! command sh -c ... [BUG] Unable to use compodoc with Apple Silicon M1...
Read more >Dependency Error in Macbook Pro m1… - Apple Developer
Dependency Error in Macbook Pro m1 Xcode 12.5.1 Version in my Other Macbook ... is done to work around a dependency that's not...
Read more >Error: Unable to run docker-compose on Apple M1 Silicon
I am using the M1 Docker Preview. Do you have instructions on how I can run the x86 version via translation? When I...
Read more >Options - Compodoc
--coverageTestThresholdFail [boolean], Test command of documentation coverage (global or per file) will fail with error or just warn user (true: error, ...
Read more >M1 Mac: Cannot build packages requiring compilation - General
I cannot install basically any package that requires compilation as it fails every time with error messages that don't mean anything to me....
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
Update compodoc to 1.1.17 version, which use a fixed version of colors, which is the origin of this error.
Ok, fixed with compodoc 1.1.18