Skip to content
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

Version parameter has side effect on expected default behavior of clientlib utility. #50

Open
ksuayan opened this issue Dec 15, 2022 · 0 comments

Comments

@ksuayan
Copy link

ksuayan commented Dec 15, 2022

aem-clientlib-generator when invoked with the --version parameter will not execute its functionality, moreso suppress the output of the --verbose switch!

package.json entry

  "scripts": {
...
    "cl": "clientlib --verbose --version",
...
  },
$ yarn run cl

I was puzzled why after running several maven builds on my local machine, I was not seeing the transpiled code getting deployed in AEM. One would expect that the --version parameter would not have any side effect and that it would merely print out the version of code to standard output.

This NPM is responsible for copying over transpiled output from ui.frontend into ui.apps as an AEM ClientLib. I realized that something was wrong after I deleted the contents of clientlib-site in ui.apps and nothing was getting generated after invoking it through yarn/npm.

The above is not a sensible default behavior for a command line utility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant