I'm testing out madge on my TS RN codebase, and I'm surprised to see that it just magically works without specifying a tsconfig.

For example
yarn madge --circular --extensions ts,tsx ./

Although this is cool and exciting, it gives me pause because the documentation doesn't explain how this works. I read the source and followed the path through a series of external npm dependencies. Af

Background: I have a pull request into a repository where the npm module isn't up-to-date with master, and I'd like to test out my branch in a module that depends on it through a bunch of different deep dependencies. It seems like patch-package would be a great solution for this.

Problem: When I append .patch to my GitHub URL it gives me a patch, but when I pass it to patch -p1 it

Is your feature request related to a problem? Please describe.

Not related to a problem

Describe the solution you'd like

We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.

_Edit from @arschles - we have focused this issue to just the twitte

Is my understanding correct that running just the yalc commands as documented won't address various issues with yarn link, such as not installing transitive dependencies and not installing new/renamed bin scripts? (It's reasons like these that were our main motivation for looking into yalc in the first place.)

I spent some time experimenting, and it seems that running `rm -rf node_module

While inspecting the installer, I noticed the fallbacks for Linux / OSX when appdirs isn't available (in data_dir()).

Wouldn't it make sense to add an if for Windows based on %APPDATA% or %LOCALAPPDATA%, before resorting to globally installing appdirs?

I walked through the various repos (dependabot-script, dependabot-core) for Dependabot, but haven't found any suitable documentation that covers the following stuff:

• How to run Dependabot with self-hosted GitHub, so that I could use it in the same way like I do regularly on GitHub with UI (e.g.

coursier provides an option to print a reversed tree of dependencies (your package being the leaves).
It could be nice to provide this kind of option for tasks like dependencyBrowseTree.

Description

Running the following Command:

./scancode -clp --json-pp sample_filter_clues.json samples --filter-clues

Gives the Error:

ERROR: failed to run post-scan plugin: filter-clues:
Traceback (most recent call last):
  File "/home/ayansm/Desktop/GSoD/scancode-toolkit-versions/scancode-toolkit-3.1.1/src/scancode/cli.py", line 1033, in run_codebase_plugins
    plugin.p

Using SourceRank via cli returns dict of SourceRank attributes instead of a single int, as shown in the API docs. Docs need updated.

SourceRank API docs at https://libraries.io/api

Project SourceRank
Get breakdown of SourceRank score for a given project.

GET https://libraries.io/api/:platform/:name/sourcerank?api_key=abc123

Example: `https://libraries.io/api/NPM/base62/sourcerank?a

See scala/scala-xml#359 (comment).

Currently licensed includes files matching:

LEGAL_FILES = /\A(AUTHORS|COPYING|NOTICE|LEGAL)(?:\..*)?\z/i

I think COPYING is superfluous, see #84, but there are some other files (also with any extension) that often include legal notices that would be useful to automatically collect, eg:

• LICENSES, NOTICES (plural)
• THIRD-PARTY-LICENSE (variations including 3rd, n

Apologies for asking, but I don't understand how any of this works, wandering in a black hole ...

1. When I launch Time Machine all my projects, vendor and node_modules are still there.
2. When I run sudo mdfind "com_apple_backup_excludeItem = 'com.apple.backupd' none of the vendor/node_modules, dirs are listed.

I launched the daemon a few days ago and thought that the newer backups would

After encountering dependency-check-team/dependency-check#112 I tried looking into how that project uses detective and the various "extensions", such as detective-typescript that enabled foreign syntax. It was not immediately obvious how this worked, seeing no explicit interfaces where detective was wrapped by or passed some "extension"

Could

The notice-pre-processor.kts file allows for customisation of the generated notice file, see https://github.com/oss-review-toolkit/ort/blob/master/docs/notice-pre-processor-kts.md.

Not all customisations seem possible, though. I would like to:

• customize the notice separator
• get rid of the separator between the different headers
• include the license name/id before the license text

Copy/paste of issue #78 (which was a copy/paste of issue #66 which was a copy/paste of #24), but for the new version 4.3.3

Hi!

I'm noticing version 4.3.3 exists for com.google.gms:google-services, and the official documentation here https://developers.google.com/android/guides/google-services-plugin mentions 4.3.3.

I was hoping to know what changed since 4.3.2 ;)

Note, in issue #66, a

Hello!

SASS has partials, which filenames start with _, but it's not written in @import: https://sass-lang.com/documentation/at-rules/import

So, we're having incorrect links (with 404).

Example: https://github.com/nana-4/materia-theme/blob/8988c72/src/chrome/chrome-scrollbar-dark/scrollbars.scss

Incorrect link to https://github.com/nana-4/materia-theme/blob/8988c72/src/_sass/colors

When writing the Gemfile_next.lock snapshot, we resolve the dependencies remotely https://github.com/Shopify/bootboot/blob/master/lib/bootboot/gemfile_next_auto_sync.rb#L56
this is unnecessary as all the gems should already have been fetched.

Resolving the dependencies locally with Bundler::Definition#resolve_with_cache https://github.com/bundler/bundler/blob/a63a39d738865665f714f179fe42dd

The plugin should in addition of reordering dependencies also format them in order to have consistent look and feel.

Example:

    implementation 'org.apache.commons:commons-lang3:3.7'
    implementation "org.springframework.hateoas:spring-hateoas"
    annotationProcessor("org.projectlombok:lombok:1.18.2")

->

    implementation("org.apache.commons:commons-lang3:3.7")
    imp

Optional dependencies should not be treated as a "dependency" kind, of which there are only three -- regular, build, and dev. "Optional deps" should instead be handled as a boolean flag, which is what cargo does. A dependency can be both a build dependency and optional simultaneously, but currently cargo-deps will erase one of these.

Optional dependencies can be displayed with a dashed line.

We don't need to transpile certain babel env plugins that are disabled by the user in their Babel env settings.

We could sniff this from user's Babel config.

Or at least provide an option here to manually override considering certain babel env plugins from consideration for transpiling.