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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--outdir
file path not reflected in package.json
#40
Comments
Ugh, sorry about that. I had the feeling I'd forgotten something. Should be fixed in 0.3.4, thanks for reporting! |
Haha, no worries. Greatly appreciate how fast you address issues! Unfortunately, this fix is outputting the path as |
Thats weird, which command are you running and which OS are you on? I just call path.join on whatever the outdir is and 'custom-elements.json' |
Yeah, I was looking at the changes you made and it shouldn't have affected the output. Strange. I'm on Windows 10 Enterprise, and running the command via a node script in my
{
"devDependencies": {
"@custom-elements-manifest/analyzer": "^0.3.4"
},
"scripts": {
"analyze": "cem analyze --globs src/zui-*.ts --litelement --outdir dist"
}
} Command I run: yarn run analyze Output in {
"devDependencies": {
"@custom-elements-manifest/analyzer": "^0.3.4"
},
"scripts": {
"analyze": "cem analyze --globs src/zui-*.ts --litelement --outdir dist"
},
"customElements": "dist\\custom-elements.json"
} Must be a Windows thing? |
Hm, looks like I might have to Also, does the actual json file get output to the dist folder correctly? |
Yeah, that sounds right to me. And yep, |
Checklist
--dev
flag to get more information?Bug
I set the output directory for my manifest file to
/dist/
, but it is not reflected inpackage.json
after runningcem analyze
script.Expected behavior
I expect that if I set
--outdir
todist
in the script,--outdir
will be reflected inpackage.json
:Command:
package.json
:The text was updated successfully, but these errors were encountered: