Document how to set up the plugin so that it does not break custom repository configuration

[jacek-lewandowski]

It would be helpful to document this approach. I've found it annoying that my project started complaining about all other dependencies which are usually fetched from a custom repository once I added this plugin.

// Append this to the bottom of your settings.gradle.kts
dependencyResolutionManagement {
  repositories {

    ivy {
      url = uri("https://nodejs.org/dist")
      patternLayout {
        artifact("v[revision]/[artifact]-v[revision]-[classifier].[ext]")
        artifact("v[revision]/[artifact]-v[revision].[ext]")
      }
 
      metadataSources {
        artifact()
      }
    
      content {
        includeGroup("org.nodejs")
      }
    }
  }
}

and

// Node configuration
node {
  version.set("xx.yy.zz")
  download.set(true)
  nodeProjectDir.set(file("${projectDir}/..."))
  distBaseUrl = null
}

[deepy]

I'm afraid I'm going to need a bit more information on this, could you show one of the complaints from gradle?

If you're using centralized repositories we do have an entry in the FAQ at: Is this plugin compatible with centralized repositories declaration?