Skip to content

[Yarn] First-use experience has some issues #307

Closed as not planned
Closed as not planned

Description

@oliversalzburg

I wish I got off the ground with CycloneDX, instead I got this. Please note that the project is built with yarn.

$ yarn cyclonedx-bom                     
Workspace (npm lockfile v2) support is experimental. Pass `--with-workspace` flag to enable and cross your fingers. Good luck!

$ yarn cyclonedx-bom --with-workspace 
error: unknown option '--with-workspace'

Activity

  1. jkowalleck commented on Jun 9, 2022

    @jkowalleck
    Member

    Described behaviour seams to be related to yarn, not this project.
    Not an issue, not a question. Closed.

  2. changed the title [-]First-use experience has some issues[/-] [+][Yarn] First-use experience has some issues[/+] on Jun 9, 2022
  3. oliversalzburg commented on Jun 9, 2022

    @oliversalzburg
    Author

    You might want to adjust the documentation of this project then, if you're "Node.js module" processor doesn't actually support NodeJS projects, but only a specific subset of them. If you require the project to have been installed with a specific package manager, that should be made clear.

    In case you're not aware, NodeJS ships with npm, pnpm, and yearn. Not even anticipating the use of these officially supported package manager is a fault of this project.

  4. jkowalleck commented on Jun 9, 2022

    @jkowalleck
    Member

    Does your used yarn version support workspaces?
    Are you sure you are using yarn correctly?
    Are you sure you are using cyclonedx-node correctly? how was is installed?
    The mentioned error message and behavior seams to be coming from yarn, or is it caused by this project? Could you provide a reproducible setup?

  5. jkowalleck commented on Jun 9, 2022

    @jkowalleck
    Member

    In case you're not aware, NodeJS ships with npm, pnpm, and yearn. Not even anticipating the use of these officially supported package manager is a fault of this project.

    the contrary is the case.
    have a look at the existing feature requests (issues) of the project and see the existing integration tests.
    this project supports npm and yarn-version-1 - both working as intended and has integration-tests for these environments.
    this project has some issues with yarn-version-2 support, as the current list of issues show.

  6. oliversalzburg commented on Jun 10, 2022

    @oliversalzburg
    Author

    The fact that these errors are due to the lack of support for yarn above version 1 is not clear to consumers. Thanks for pointing out that you are already aware of the lack of support; the potential consumers of your project are likely not.

    I was reporting on a first-use experience issue. I didn't plan to get involved in your project, read all your issues and your source to try and resolve standing issues with your implementation. If you are not open to improve your project in that regard, that is fine with me. At this point there is probably zero chance that I would be using something you built.

    Have a nice day.

  7. jkowalleck commented on Jun 10, 2022

    @jkowalleck
    Member

    Lets start again:
    Hello, I am the current maintainer of this project. I am not the author, builder, etc. I am just the person keeping things together.
    So, your first experience was not great? Please tell what you did, what you expected to happen, what actually happened. Most importantly, please describe how you cam to the expectations, so it gets clear which documentation could be improved.
    Could you elaborate what the CLI copy-paste is supposed to mean? Could you provide/describe a reproducible example/setup for it?

  8. locked and limited conversation to collaborators on Jun 12, 2022
  9. converted this issue into a discussion #310 on Jun 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions