Closed exactlyaron closed 6 years ago
Oh wait I think this is because of the parse-domain package issue. 😕
The package should works properly.
It seems your problem is related to npm not to this package specifically.
It might be caused by the parse-domain
but I can't be sure without seeing the rest of the logs.
Hi, ok thanks, here is a log from Travis when it's failed. travis_log.txt You may spot something that I haven't.
Is the conventional-changelog-metahub
present in your package.json
devDependencies?
Yeah it is.
"devDependencies": {
"cz-conventional-changelog": "2.1.0",
"semantic-release": "^15.5.2",
"conventional-changelog-metahub": "^2.0.2"
I'll run a debug build and check it's actually getting installed.
Yep definitely installed and in node_modules.
Seem to have resolved it by adding skip_cleanup: true
to the Travis config.
Ok, it can be closed then I guess.
Hi @pvdlg
Firstly I guess I should ask if this package is still up to date and working as far as you know?
It looks ideal in terms of the release types and the formatting and emojis are cool. I've been playing around the commit-analyzer then seen this so it would be quick to test it and then modify as needed rather than building out the standard angular one but I keep getting a module not found error in Travis CI.
I've had a search and found the following issues, here, here and here.
So I've done the things recommended in those issues, stopped caching /.npm, removed cache from within the Travis build UI,
Using
install: - travis_retry npm install
instead of the normalnpm install
But get
It's a private build so can't link to the travis log. But I can send you a copy of the raw if needs be. Semantic-releases shows now errors when loading the plugins etc.
The package.json reelase config is as follows
Basically the same as how you've done it here
Thanks for any help! 👍