TypeStrong / TypeStrong/ts-loader

Cannot reference parent yarn workspace g:ts-node script

Open
#1,510 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.5k
Forks
439
Avg merge
17h 17m
Merged PRs (30d)
2

Description

Expected Behaviour

I can use parent yarn workspace ts-node with the g:ts-node syntax as outlined in https://yarnpkg.com/getting-started/qa#how-to-share-scripts-between-workspaces so I do not need to list the ts-node as a direct dependency of the child workspace that is doing the webpack compilation

Actual Behaviour

I am forced to create a duplicate dependency on ts-node in the child yarn workspace

Steps to Reproduce the Problem

Have a root/parent yarn workspace with the ts-node devDependency and add a "g:ts-node": "cd $INIT_CWD && ts-node" script so g:ts-node can be used from any child yarn workspace. Create a child yarn workspace and set it up to compile webpack with ts-node. There is no way to use the g:ts-node.

Location of a Minimal Repository that Demonstrates the Issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the parent and child Yarn workspace setup described in the issue, including the root g:ts-node script and the child webpack compilation. Trace how the workspace resolves that script and verify completion when the child can invoke g:ts-node without declaring ts-node as a direct dependency.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, webpack
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.