Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Package names ignored
See original GitHub issueMali ignores package names when defining services, e.g. mali.use('TestService', ...) instead of mali.use('test.TestService' ...). I’ve not tested what happens if services in different packages have the same name, but nevertheless I think package names should be required in service definition process.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
no-extraneous-packages should ignore invalid package names
Package names that are invalid in npm most likely use custom resolvers and won't be extraneous.
Read more >How to exclude package name and sub ... - Stack Overflow
The correct rule for keeping everything in package in.myapplication.app.samplePackage and all subpackages is:
Read more >ignore-package-name-case
If the value of this variable is true, then the case of characters in single-case package names and nicknames is ignored by the...
Read more >Ignore packages that are not currently installed when using ...
ubuntu - Ignore packages that are not currently installed when using "apt-get remove" - Super User. Stack Overflow for Teams – Start collaborating...
Read more >Ignoring Code - ESLint - Pluggable JavaScript Linter
You can configure ESLint to ignore certain files and directories while linting by ... in package.json for the eslintIgnore key to check for...
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 Free
Top 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
Hello, this should be fixed in 0.14.0. You can use full package definition to reference a service:
Sorry maybe I needed more coffee hah. Don’t know what I was saying in my comment lol… We can specify service name, not package name… I’ll have to investigate this. I am not sure if you can have more than 1 package that defines services in grpc, but if you can this could be an issue. Thanks.