Skip to content

Adjustments to run outside maintainer org #1

@losolio

Description

@losolio

When trying to run structor-export outside the maintainer environment, I ran into a couple of manageable blockers:

  1. package-lock.json is linked to an internal package registry (pkgs.dev.azure.com/nhnfelles), however the same packages are mostly available as public packages as well. Dirty fix is that deleting package-lock.json unlinks from azure registry and enables the installation from npmjs
  2. @helsenorge/core-build package seems to be used only for vitest config. This package is not publicly available, which prevents installation. Dirty fix for running is just removing the dependency from package.json allows the solution to install
  3. husky. .husky is missing and husky is not listed as a (dev)dependency. The prepare script therefore fails. Dirty fix for running is just removing the prepare script allows the repo to install and run.

Perhaps some of it could be adjusted to make it easier to clone and test this?

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