Skip to content

Version mismatches #87

Description

@idleberg

I have noticed a couple of version mismatches for the NodesJS packages:

  • the local @pkl-community/pkl package is versioned 0.25.1
  • the local @pkl-community/pkl-eval package consumes @pkl-community/pkl@0.28.2
  • the latest version published on npm is @pkl-community/pkl@0.30.2

I would recommend that you setup a workspace and consider using automated releases. Workspaces are a feature provided by all major NodeJS package managers and they allow referencing local versions. The dependencies of @pkl-community/pkl-eval would then look like this:

{
  "dependencies": {
    "@pkl-community/pkl": "*"
  }
}

Personally, I prefer using pnpm because I prefer how workspace dependencies are defined:

{
  "dependencies": {
    "@pkl-community/pkl": "workspace:*"
  }
}

That's also what kept me from submitting a PR, since I don't like forcing personal habits on others. Would such a change be welcome and if so, which flavour would you prefer?

Using workspaces also enables you to work with the TypeScript sources directly, given that you support node@>=20.20:

{
  "name" : "@pkl-community/pkl",
  "bin": "src/main.ts",
  "main": "src/index.ts",
  "publishConfig": {
    "bin": "lib/main.js",
    "main": "lib/index.js",
  }
}

By the way, is there a specific reason why the package for TypeScript bindings is not part of this repo?

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