Skip to content

Use NPM workspace commands instead of cding into package directory #961

Closed
@rmorshea

Description

@rmorshea

Current Situation

The last release of the JS package event-to-object failed because the noxfile.py attempts to publish the package by cding into the package directory and running npm install. I'm not really sure why this is a problem but it seems to do with the fact the there's only a lockfile at the project root rather than for each package (maybe related issue).

Proposed Actions

We should instead run commands for each JS package via npm --workspace <the-package> <the-command>.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority-2-moderateShould be resolved on a reasonable timeline.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy