Visitar URL original
Can we use v0.28.0-alpha.21 version in our production app · Issue #1974 · nodegit/nodegit · GitHub
Skip to content

Can we use v0.28.0-alpha.21 version in our production app #1974

Description

@LokeshNSF

System information

  • node version: 16.19.1
  • npm or yarn version: yarn 1.22.19
  • OS/version/architecture: macos
  • Applicable nodegit version: v0.28.0-alpha.21
node -v
npm -v # (or yarn -v)
node -e "console.log(process.platform)"
node -e "console.log(require('os').release())"
node -e "console.log(console.log(process.arch))"

@ianhattendorf Just wanted to check whether it is safe to use Nodegit version v0.28.0-alpha.21 in our prod app with Node 16.19.1.

Activity

  1. axkibe commented on Mar 12, 2023

    @axkibe

    I'm chiming in, I too am using nodegit in production and am starting to feel a little worried about this project, despite many issues not beeing catered for (next to little things a report about memory corruption should really be taken care of), we also have a release version with very old dependencies.

    To keep this positive, is there something you need help with?

  2. LokeshNSF commented on Mar 12, 2023

    @LokeshNSF
    Author

    Thanks @axkibe We have to upgrade nodegit as we are planning to upgrade Node in our app. I am still doing testing with this alpha version and little worried why there isn't a latest version release for long time.

    Any one who is testing / using these alpha versions in their app can comment about their experience and it will give more confidence.

  3. axkibe commented on Mar 14, 2023

    @axkibe

    I'm using nodegit v.0.27 with node 18.14.0.

    I also don't know, why the alpha is not released, asked a few times what the stopped and only got one sarcastic reply so far with "SoonTM", so cannot say.

  4. LokeshNSF commented on Mar 14, 2023

    @LokeshNSF
    Author

    I tried with v.0.27 with Node 16.19.1, but got the same issue mentioned here - #1840

  5. axkibe commented on Mar 14, 2023

    @axkibe

    Have you tried deleting your node_modules folders and package-lock.json and running npm install? That cleared these kind of errors for me. Previously I used same nodegit version with node 16.14.0 and worked too.

  6. nicolaschambrier commented on Mar 21, 2023

    @nicolaschambrier

    @axkibe did you not run into compilation-related runtime issues? I have A LOT of trouble making it work on a Docker image for production, see #1975

  7. LokeshNSF commented on Mar 21, 2023

    @LokeshNSF
    Author

    Have you tried deleting your node_modules folders and package-lock.json and running npm install? That cleared these kind of errors for me. Previously I used same nodegit version with node 16.14.0 and worked too.

    I have done all of these and it doesn't work and throws error as mentioned here - #1840

  8. axkibe commented on Mar 21, 2023

    @axkibe

    @axkibe did you not run into compilation-related runtime issues? I have A LOT of trouble making it work on a Docker image for production, see #1975

    At first I did ran into one or other issue, but installing some -dev packages it works. Don't remember tough which exactly. On debian bullseye as basis, also some Ubuntu forgot which version.

    Yes precompiled don't work, but the script compiles them for me.

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