Skip to content

make slonik a dev dependency #1

@mmkal

Description

@mmkal

Since slonik is only used for types in this and all the child packages, could it be relegated to devDependencies? The dependency in package.json (16.8.0) isn't the latest version so by using this it's causing multiple copies of slonik to end up in my node_modules.

As a separate suggestion - might it make sense for this and all the other slonik-* packages be moved to https://github.com/gajus/slonik and that repo be made a lerna/yarn monorepo? That way it'd make it easier to apply fixed versioning to packages that do depend on slonik, test, track issues etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions