Find the groupID of a pom file, potentially looking at its parent pom file. See find-parent for the meaning of the arguments.

Return the content of a .pom file.

Return the list of dependencies listed in the sxml content of the pom file.

Given pom-file, the file name of a pom, return the list of pom file names that correspond to itself and its submodules, recursively.

Find the version of a pom file, potentially looking at its parent pom file. See find-parent for the meaning of the arguments.

Convert a group ID to a directory path.

Build the given package, applying all of PHASES in order.

Build the given package, applying all of PHASES in order.

Write an assignment of VALUE to KEY to PORT.

VALUE must be a string (without any special characters such as quotes), a boolean or an integer. Lists are currently not supported

Write a section header for a section named SECTION-NAME to PORT.

Write the assignments in ALIST, an association list, to PORT.

Build the given JavaScript package, applying all of PHASES in order.

Build the given Mix package, applying all of PHASES in order.

Provides a lambda to supply to modify-json which replaces the value of the supplied field. `fields` is a list of pairs, where the first element is the field-path and the second element is the value to replace the target with. Examples: (replace-fields '( (("path" "to" "field") "new field value") ("path.to.other.field" "new field value")))

Like 'with-atomic-file-replacement', but PROC is called with a single argument---the result of parsing FILE's contents as json---and should a value to be written as json to the replacement FILE.

Provides a lambda to supply to modify-json which modifies the specified json file. - `fields` is a list procedure-specific data structures which should include the definition of a `field-path` in one of two syntaxes: dot-syntax string such as `"devDependencies.esbuild"`, or a list of strings such as `(list "devDependencies" "esbuild")`. - `field-modifier` is a lambda which is invoked at the position of the field. It is supplied with the current field definition, the association list (alist) at the field location in the json file, and the field name, also called `key`. - `field-path-mapper` is a lambda which instructs where the field-path is located within the field structure. - `insert?` allows the creation of the field and any missing intermediate fields. - `strict?` causes an error to be thrown if the exact field-path is not found in the data

Provides a lambda to supply to modify-json which deletes the specified `fields` which is a list of field-paths as mentioned in `modify-json-fields`. Examples: (delete-fields '( ("path" "to" "field") "path.to.other.field"))

Rewrite 'package.json' to allow the build to proceed without packages listed in 'dependencies-to-remove', a list of strings naming npm packages.

To prevent the deleted dependencies from being reintroduced, use this function only after the 'patch-dependencies' phase.