Ability to match `glob` symlink behavior

Open
#97 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start by reproducing the failing test in the @vercel/nft migration described in the issue and trace how tinyglobby handles glob patterns involving symbolic links. Compare the behavior with the documented glob rule for ** patterns. Done means the relevant test passes with matching symlink behavior.

Written by the indexing model from the issue text.

Description

I've been trying to switch @vercel/nft over to tinyglobby from glob. There's one failing test and I'm pretty sure it's because of the symlink behavior that glob has

From https://www.npmjs.com/package/glob:

By default, a ** in a pattern will follow 1 symbolic link if it is not the first item in the pattern, or none if it is the first item in the pattern, following the same behavior as Bash.

Dominant language
TypeScript
Stars
544
Forks
30
PR merge metrics
No merged PRs in 30d

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.

More from SuperchupuDev/tinyglobby

All issues in SuperchupuDev/tinyglobby

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.