We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey team 馃槈
I tried using outdir in my custom-elements-manifest.config.mjs but the file still gets generated at the default location. Using the CLI param works.
outdir
custom-elements-manifest.config.mjs
export default { globs: ['src/**/cc-*.js'], // Has no effect for now outdir: 'dist', plugins: [ ], };
The text was updated successfully, but these errors were encountered:
Also, when I specify --outdir dist and dist does not exist, there's an ENOENT error.
--outdir dist
dist
ENOENT
Sorry, something went wrong.
Ah, its because the defaultValue of outdir (from the CLI options) is '', and CLI options override user config options;
defaultValue
''
const mergedOptions = { ...userConfig, ...cliConfig };
And because outdir (from CLI options) has a value (''), I guess it overrides the user config option 馃う
fixed in #49
馃 馃暫
@thepassle There is still an error if the directory does not exist:
No branches or pull requests
Hey team 馃槈
I tried using
outdir
in mycustom-elements-manifest.config.mjs
but the file still gets generated at the default location. Using the CLI param works.The text was updated successfully, but these errors were encountered: