Search fails for scoped packages
See original GitHub issueDescribe the bug
When searching for scoped packages like @company/core
, the search returns “No results found”.
To Reproduce
- Start a fresh instance of the latest Verdaccio version. (e.g. latest available docker image).
- Publish a scoped package
@company/core
. - Open Verdaccio and search for
@company/core
.
Expected behavior
The search result should list the scoped package.
Additional context
The bug seems to be a server issue, because in the network log /-/verdaccio/search/ returns an empty array. Propably the describe behavior is related to an inapropriate URL decoding.
Please let me know, if you need further input.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
TSC not find imported scoped packages. #27126 - GitHub
The scope is basically an NPM namespace to prevent collision of package names. Actual behavior: TSC fails to find the packages. Here's the...
Read more >NPM is failing to install any scoped packages - Stack Overflow
My issue is that I'm unable to install any scoped packages. Everything returns with a 404 Not Found. Here's some examples to list:...
Read more >Scoped registries - Unity - Manual
Scoped registries allow Unity to communicate the location of any custom package registry server to the Package Manager so that the user has...
Read more >npm Registry - JFrog - JFrog Documentation
For scoped packages, use the following command: ... with a transient user, npm login will fail as the user is not registered in...
Read more >npm packages in the Package Registry - GitLab Docs
Scoped packages begin with a @ have the format of @owner/package-name . ... Due to a bug in npm 6.9.0, deleting distribution tags...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like an issue with the lunr-mutable-indexes lib. Looks like lunr.js has had a few open issues for special characters but none that were addressed.
What I see from the ‘@’ sign is that is this ignored during indexing.
If I have a package
@sample/sample
and index.search(‘sam*’) this will return back @sample/sample.One possible solution is to ignore special characters (not ideal but should get the user what they are looking for) Another is see if we can get a fix in for lunr.js and handling of special characters.
I have this question, the first search.
Ordinary text can retrieve internal ones, but it’s not good to start with @.
Then after searching once, @ will take effect again. Magic.