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.
Conflict with alias @
See original GitHub issueConflict with alias @ with some packages like the new font awesome 5
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Resolving alias conflicts - IBM
Resolving alias conflicts ... An object structure that contains multiple objects and supports flat files or interface tables, cannot have duplicate field names ......
Read more >Resolve an AD Alias Conflict With a Local Account
This topic covers the two options to resolve file-ownership conflicts that occur under certain conditions when a user logs on with an AD...
Read more >Alias: An approach to .NET Assembly Conflict Resolution
Alias performs the following steps: ... The result is a group of files that will not conflict with any assemblies loaded in the...
Read more >What is the expected behavior when Username Alias conflicts ...
Alias conflicts can occur in several different ways. Let's assume the primary usernames already exist in Duo and an admin populates a new...
Read more >How to test for possible conflicts while using alias in bashrc?
Is there a simple way to list all the command conflicts that have occurred in the system due to the bashrc update involving...
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
Thanks for the feedback, that’s a great list of possible replacements.
Personally like $ or #, but I’m afraid t least $ could be problematic because it’s used as a special chat in aliases, defining the end of the require string.
I’ll play a bit wirh both to check for limitations, and ask everyone who’s interested to do the same.
Because there might be packages whose name starts with
src.