Gar

Yes it's not very well documented, but the way "globstar" is treated got aligned more with standard glob implementations quite some time ago. Not sure what the long term solution...

Added a note to our [v11 roadmap](https://github.com/npm/statusboard/issues/488#issuecomment-2107832837) to unwind all of these hacks.

> What does 'unwind all of these hacks' mean? It means no longer work around the default `node-glob` behavior. The decision was made at the time to try to work...

For what it's worth `find` does not use "glob". `ls` does. Compare the difference between `ls *` and `ls */*`

Yes those last two would be what npm 11 does.

These questions show just how wanting we are for a proper spec here. I don't have answers today. The way it works now is not working. That's the only answer...

If you look through the history of especially `map-workspaces` and `npm-packlist` you'll see just how buggy the changes from `glob` have made npm. We have to work around the new...

https://github.com/npm/npm-packlist/blob/cb4a823cd42d50475a8e1e7582b95b15766f5ca2/lib/index.js#L25

Duplicated in a workspace off of `latest` ``` @wraithgar ➜ /workspaces/cli (latest) $ npx [email protected] --version 8.3.0 @wraithgar ➜ /workspaces/cli (latest) $ npm ls -g /usr/local/share/nvm/versions/node/v20.12.1/lib ├── [email protected] ├── [email protected]...

Can you go into more detail about how you fix up the lockfile?