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

Installation issues #425

Closed
fgadaleta opened this issue Dec 21, 2022 · 10 comments · Fixed by #501
Closed

Installation issues #425

fgadaleta opened this issue Dec 21, 2022 · 10 comments · Fixed by #501
Labels
bug Something isn't working released

Comments

@fgadaleta
Copy link

Debian package seems to be corrupt.

npm install from the cloned repo terminates with errors

sudo npm install -g @asyncapi
npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "@asyncapi": Tags may not have any characters that encodeURIComponent encodes.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-12-21T11_05_40_874Z-debug-0.log
(base) frag@daedalus:~/c0ding/asyncapi/generator$ sudo npm install -g @asyncapi/ag
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@asyncapi%2fag - Not found
npm ERR! 404 
npm ERR! 404  '@asyncapi/ag@*' is not in this registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-12-21T11_05_56_154Z-debug-0.log
(base) frag@daedalus:~/c0ding/asyncapi/generator$ npm install 

up to date, audited 1247 packages in 30s

47 packages are looking for funding
  run `npm fund` for details

20 vulnerabilities (17 moderate, 2 high, 1 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

How to install the generator?

@fgadaleta fgadaleta added the bug Something isn't working label Dec 21, 2022
@github-actions
Copy link
Contributor

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link
Member

derberg commented Dec 21, 2022

Hey, sorry but packages like @asyncapi and @asyncapi/ag do not exist.

You install generator with @asyncapi/generator if you want to use it as library. In case of CLI I think in docs we already suggest to perform installation of the AsyncAPI CLI, so @asyncapi/cli

@fgadaleta
Copy link
Author

even that fails

I install with

sudo npm install -g @asyncapi/cli
[sudo] password for frag: 
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@asyncapi/modelina@0.59.9',
npm WARN EBADENGINE   required: { node: '>=14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@oclif/core@1.22.0',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'yaml@2.2.0',
npm WARN EBADENGINE   required: { node: '>= 14' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated readdir-scoped-modules@1.1.0: This functionality has been moved to @npmcli/fs
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

changed 923 packages, and audited 924 packages in 31s

89 packages are looking for funding
  run `npm fund` for details

8 moderate severity vulnerabilities

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

and then run

$ asyncapi 
/usr/local/lib/node_modules/@asyncapi/cli/node_modules/@oclif/core/lib/command.js:41
            delete this.globalFlags?.json;
                                    ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/@asyncapi/cli/node_modules/@oclif/core/lib/index.js:6:19)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

@asyncapi-bot
Copy link
Contributor

Hello, @fgadaleta! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

  • /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
    example: /gfi js or /good-first-issue ci-cd

Copy link
Member

derberg commented Dec 21, 2022

these are weird 🤔
do you normally use Node and npm or just for the CLI? maybe just go ahead and try different installation options https://github.com/asyncapi/cli#installation. We provide binaries that do not require node and npm.

@fgadaleta
Copy link
Author

I tried other methods too.
Debian package seems corrupt and tar.gz too
Maybe links are broken?

Can you check?

Copy link
Member

derberg commented Jan 11, 2023

Sorry, I was out for some time.
Damn, you are right, the links there are broken. Looks like we do not publish these packs for releases anymore. It is all red https://github.com/asyncapi/cli/actions/workflows/upload-release-assets.yml and so far I have no idea why. Will have to investigate, sorry about that

@derberg derberg transferred this issue from asyncapi/generator Jan 12, 2023
@github-actions
Copy link
Contributor

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@derberg
Copy link
Member

derberg commented Jan 12, 2023

Moved it to CLI repo as we anyway will deprecate Generator CLI.
More critical is to fix installation for CLI.

I just do not know what the solution is so far.

@asyncapi-bot
Copy link
Contributor

🎉 This issue has been resolved in version 0.37.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants