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.
Scoped packaged not using the correct name
See original GitHub issueSince the string passed to lass starts with @ it should prompt to use @ladjs/email as the package name not just the directory name.
➜ code lass @ladjs/email
> Generating package in /Users/xo/code/@ladjs/email
? What is the name of the new package (email)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
scope - npm Docs
When used in package names, scopes are preceded by an @ symbol and followed by a slash, e.g. ... Scoped packages are not...
Read more >npm - Understanding Scoped Packages - Nitay Neeman's Blog
Scoped Packages is a way to group related npm packages together, and connect them to each other by a specified “scope”, that acts...
Read more >Doesn't work with scoped packages (@scope/package-name)
Using scoped packages with names like @avatsaev/my-lib doesn't structure the artifacts correctly, so the final result can't be packaged.
Read more >NPM is failing to install any scoped packages - Stack Overflow
I'm on Node v6.10.3 and NPM v3.8.6. My issue is that I'm unable to install any scoped packages. Everything returns with a 404...
Read more >npm Registry - JFrog - JFrog Documentation
https://<server name>.jfrog.io/artifactory/api/npm/<repository key>. To use the npm ... For scoped packages, use the following command:.
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
Maybe we should make the
configOptionsand thecontextargument inposthook consistent 😅 and hopefully removecontextargument in post hook in next major version.This was fixed on https://github.com/lassjs/lass/pull/32