{"_id":"@eclipse-cdt-cloud/clangd-contexts","_rev":"8-fd1635842efc4986750bb969064a6aca","name":"@eclipse-cdt-cloud/clangd-contexts","dist-tags":{"next":"0.9.0-next.48df6c3.0","latest":"0.9.0-next.c7c35a6.0"},"versions":{"0.9.0-next.c7c35a6.0":{"name":"@eclipse-cdt-cloud/clangd-contexts","displayName":"CDT.cloud Clangd Contexts","description":"CDT.cloud - Support for multiple configuration contexts in clangd.","version":"0.9.0-next.c7c35a6.0","license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","publishConfig":{"access":"public"},"keywords":["cpp","clangd"],"dependencies":{"js-yaml":"^4.1.0"},"devDependencies":{"@types/chai-string":"^1.4.2","@types/js-yaml":"^4.0.2","@types/node":"~12","chai-string":"^1.5.0"},"scripts":{"clean":"rimraf lib *.tsbuildinfo && rimraf .eslintcache && rimraf .nyc_output coverage","lint":"if-env SKIP_LINT=true && echo 'skip lint check' || eslint --cache=true --no-error-on-unmatched-pattern=true \"{src,test}/**/*.{ts,tsx}\"","build":"tsc -b compile.tsconfig.json","test":"mocha --config ../../configs/mocharc.json \"./lib/**/*.*spec.js\""},"main":"lib/index","types":"lib/index","nyc":{"extends":"../../configs/nyc.json"},"gitHead":"c7c35a61b33085825fdf69573ed10a0f1a86bcd6","_id":"@eclipse-cdt-cloud/clangd-contexts@0.9.0-next.c7c35a6.0","_nodeVersion":"12.22.10","_npmVersion":"lerna/4.0.0/node@v12.22.10+x64 (linux)","dist":{"integrity":"sha512-5onxqnGhAKAg5SVloFbo4X6to9OA7jpjbEGVwUfNUkoj5rsLVzETTOPZJu98mTGiuMOrt9nyUpvdINK3ItkgjA==","shasum":"200bd80f14cd30828db68924cfb64592dfcb736c","tarball":"https://registry.npmjs.org/@eclipse-cdt-cloud/clangd-contexts/-/clangd-contexts-0.9.0-next.c7c35a6.0.tgz","fileCount":51,"unpackedSize":127988,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiDki2ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpHxQ/9HMQ/k7K7NtkQiWlbLrS/FO1O+a7SEvoH/uHBPJIttglkYENe\r\nSIpbRCllnM0huVaxQdS3ZIIkM6i48q7OVZwBJgQZ01zLUzUjgUYk3M10JiI9\r\nBA3XoX9bDQ4Lr7FZwh30DTvl8cSZelpOcXBNNKVEe0Mjwie3WEp6dIlvvE8C\r\nJE01oqIyKLkg/aAvAxCfoggeZEWaaghNxLDUj/aaQDX7UnreOWSjiCj2OAGA\r\n+kqtXVI89if5zAXEkhhn+S7H6thyu7Kxg6EEHNp+hQPZjOgl4/26UHF/mtNc\r\nPOJZ9Xg+rROukRmUiMoKF9J9m1IRFkWrii2y8kGV9A4SYchk585aeeydIO4y\r\nf9LgQSmQFAqiRwPe2nSP4xH5WFUagEyFHWKG8BEPVUE1sVXbUXH9qj9StZ3V\r\nunfSx24sc2ZBKYma3uDTI8zNxA0vXFqpRibT9w4PjPC5nvtbJKAdeO+HBBPN\r\nG0kGUn3uNOBYernSgnwlLFa7EFpE3fOJxTURrcmSEzLF8nWLBylilTmCRjKo\r\nUDI/SvwqdliiK0Y5gWqm3DM8IbRZ5uwo3WhfFpf+Q2eBo1K/s5UyD3VAMEeR\r\nUBE7dipQWB13unX4p9SIXSvET5rzrfSCA4vs9+dqQO/lW6GdNxewb4K7hNKQ\r\noqvd9f6b7VKZR0Hj4wXjjDkhtT+PCSZIuyY=\r\n=8+Qr\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDy6UcLHr1jvdAh69ZX+XA8dSY5inN4TnUQR6anEIjhAQIhAKBEcd6wsI/WUKWOZA7G1IoXxHXBaqcipuTtLsBIiwl5"}]},"_npmUser":{"name":"eclipse-cloud-bot","email":"cloud-bot@eclipse.org"},"directories":{},"maintainers":[{"name":"eclipse-cloud-bot","email":"cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/clangd-contexts_0.9.0-next.c7c35a6.0_1645103286093_0.7169575338617273"},"_hasShrinkwrap":false},"0.9.0-next.47b67f9.0":{"name":"@eclipse-cdt-cloud/clangd-contexts","displayName":"CDT.cloud Clangd Contexts","description":"CDT.cloud - Support for multiple configuration contexts in clangd.","version":"0.9.0-next.47b67f9.0","license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","publishConfig":{"access":"public"},"keywords":["cpp","clangd"],"dependencies":{"js-yaml":"^4.1.0"},"devDependencies":{"@types/chai-string":"^1.4.2","@types/js-yaml":"^4.0.2","@types/node":"~12","chai-string":"^1.5.0"},"scripts":{"clean":"rimraf lib *.tsbuildinfo && rimraf .eslintcache && rimraf .nyc_output coverage","lint":"if-env SKIP_LINT=true && echo 'skip lint check' || eslint --cache=true --no-error-on-unmatched-pattern=true \"{src,test}/**/*.{ts,tsx}\"","build":"tsc -b compile.tsconfig.json","test":"mocha --config ../../configs/mocharc.json \"./lib/**/*.*spec.js\""},"main":"lib/index","types":"lib/index","nyc":{"extends":"../../configs/nyc.json"},"gitHead":"47b67f97208867fcc026b42b67c14b8b2db93821","readme":"# @eclipse-cdt-cloud/clangd-contexts\n\n## Overview\n\nAn API for management of [clangd](https://clangd.llvm.org) configuration files in C/C++ projects using _contexts_.\nA _context_ is the set of flags, parameters, other settings and source files that clangd uses as input.\nCurrently, this library is limited to configuring the compilation database (`compile_commands.json` file) and compile flags in the `.clangd` file for a project.\nContexts are identified via the names of the directories containing `compile_commands.json` files.\nIn the future additional settings may be associated with a specific context, for example the handling of additional or removed compilation flags (currently these are managed on an _ad hoc_ basis).\n\n## Features\n\n-   API for management of [clangd](https://clangd.llvm.org) configuration files\n-   retrieve and set contexts in one or more `.clangd` files\n-   manage compile flags in `.clangd` files\n\nThe API in the `clangd-config` and `clangd-context` modules manages the `CompileFlags` configuration of _clangd_ in the `.clangd` files in a C/C++ project.\nIn particular,\n\n-   which `CompilationDatabase` to use, referencing a `compile_commands.json` file\n-   any compiler flags to `Remove` from or `Add` to those specified in the compilation database when invoking `clang`\n\nThe API establishes two core concepts: a _project_ that is configured via a `.clangd` file and a _context_ that identifies a compilation database (a particular `compile_commands.json` file).\nA context's name is inferred from the name of the directory that contains the compilation database file.\nA workspace may have one or more projects each configured with a `.clangd` file for different subtrees.\nEach project has one or more contexts and in a multi-project workspace the projects' context names may overlap to any degree.\nThe [example workspace](../../examples/clangd-workspace/README.md) shows a fairly small example of how this can be laid out:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project\n  |   +-- Debug_x86-64/              // a \"Debug mode for x86-64 architecture\" context\n  |   |   +-- compile_commands.json  // the context's compilation database\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release_Atom/              // a \"Release mode for Atom architecture\" context\n  |   |   +-- compile_commands.json\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project\n      +-- Debug_x86-64/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- Release_Atom/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- .clangd                    // the clangd configuration for the \"lib\" project\n```\n\nThe core API for the `.clangd` configuration file does not assume any particular directory structure: client applications specify contexts to set into the `.clangd` file either by path to the `compile_commands.json` file or the directory containing it.\nThe inferred name of the context, which is useful primarily for presentation to the user in a UI or command-line tool, is the path name of the parent directory of the `compile_commands.json` file relative to the `.clangd` file for the project.\nSo, in the example above, the context names in both projects are \"Debug_x86-64\" and \"Release_Atom\".\n\nAnother API in the `clangd-contexts-config` module is provided to help clients discover existing projects and contexts of a workspace that is configured with an optional `.clangd-contexts` file that describes the layout of the workspace.\nA workspace may have one of these at the root or may have several `.clangd-contexts` files in different subtrees.\nA `.clangd-contexts` file enumerates the project directories in its scope and, for each, indicates whether context directories are organized in a flat list as in the example above or hierarchically as in the structure below:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project directory\n  |   +-- Debug/                     // \"Debug mode\" contexts\n  |   |   +-- x86-64/                // the \"Debug mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Debug mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release/                   // \"Release mode\" contexts\n  |   |   +-- x86-64/                // the \"Release mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Release mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project directory\n  |   +-- Debug/                     // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- Release/                   // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"lib\" project\n  +-- .clangd-contexts               // configuration of project layout in the workspace\n```\n\nThe API around the `.clangd-contexts` configuration file provides functions for querying what are the configured project directories and what are the\ndistinct context names available across all of those projects.\nIn this layout, the distinct context names are \"Debug/x86-64\", \"Debug/Atom\", \"Release/x86-64\", and \"Release/Atom\".\n\nCurrently, the `.clangd-contexts` file is limited to describing the shape of projects in the clangd workspace.\nA future enhancement should expand the configuration in this file to include lists of added/removed compile flags on a per project basis and, optionally, per context as well, allowing the `setContext` and `selectContext` APIs to update the added/removed compile flags in the `.clangd` configuration automatically on context switch.\n\n## Example Workspaces\n\n-   [`examples/clangd-workspace`](../../examples/clangd-workspace/README.md)\n    -   provides a small example workspace with two interrelated projects in which to test drive the API via the [VS Code Extension example](../../examples/clangd-contexts-ext/README.md) and/or the [CLI Example](../../examples/clangd-contexts-cli/README.md)\n\n## License\n\n-   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)\n-   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)\n","readmeFilename":"README.md","_id":"@eclipse-cdt-cloud/clangd-contexts@0.9.0-next.47b67f9.0","_nodeVersion":"12.22.10","_npmVersion":"lerna/4.0.0/node@v12.22.10+x64 (linux)","dist":{"integrity":"sha512-vK1zVGMCbvWVHRtyCoblDrMABTPpY//azgPrObDZx5kOdeVxGX55FGVLSR26D5/cXdKUEBF80u7KAPmujS6e5Q==","shasum":"f15c1a4ba5fb7735cc14008f9966b680699511dd","tarball":"https://registry.npmjs.org/@eclipse-cdt-cloud/clangd-contexts/-/clangd-contexts-0.9.0-next.47b67f9.0.tgz","fileCount":51,"unpackedSize":127988,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJiDkzwACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpQ9g/+IX2OtM+hmk8bq6odXtLftOQxt7d/0g4ohHdPVaNDsl+06slP\r\nugpm5pe0CYfAUjHj/AukMGhWwRgA4QaASajRhYC9sQ9wnYqHqG/hUd0wjJ8N\r\n8QMwqQG877Ydm10TwI4GjQY+2lSeXOEJl3Q+xcNOV5Gn0qMbY9KBiE8grJ/y\r\nTPP9lKATxZ00rehcTX2IBvToBJErPa1Im/0OX/s27zizPAOXlQ8mlZ3h3ngx\r\nVYZtypYQ2ZErWW7V0lNvAfMLDpGcsDCQuyxIfpuP4NlYTo8vulV0I28/EtQT\r\nqvvkGPiUr8DKWK9Qbjw9hpKkXAHGSPLdPyoUbxdSj6zQftmLOk5lUEr5nIjT\r\nk4LIKsnDspvRJi4Sw2+QlrG2cSmUHR5jAAAR9DrbbzMfTcL1kJIBQGZA3WNt\r\npg6TZTepx59lOy4BHnkZ3u+JhuilARPAtSg4dcOizmw3RvcXmc7kQWXqWBC6\r\nJ1YeIrpDAZZprmOOR5kmnCsLqOXHNiT/Ha5ryGv/aLJe5VGdB1oLDtTHL2Eg\r\nsoQbb+S5WLs/ZeBhHPSQsaI2wXhMP0OHHWSQJJe0S9RuxnypD4zYi7Ty4ai3\r\n6kSMbkjoGxh4u0tJzDj8m4D3Ni0CcbMshwhtY+NRIMT5gxcjnWaXLxfmICgB\r\nToUr68Iw8ihyjlSiicoa/MNMFZRvadEO0Uc=\r\n=vgos\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCuYl1B5EpwY0vNV3zUUU9dhjn9WKiPzDw4N5nv+j2krQIhAPs0PF4RGYLhzJcvoSneIPkiB7czn91vmtTtNF2bKt24"}]},"_npmUser":{"name":"eclipse-cloud-bot","email":"cloud-bot@eclipse.org"},"directories":{},"maintainers":[{"name":"eclipse-cloud-bot","email":"cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/clangd-contexts_0.9.0-next.47b67f9.0_1645104368022_0.6820973665974654"},"_hasShrinkwrap":false},"0.9.0-next.4e06ecd.0":{"name":"@eclipse-cdt-cloud/clangd-contexts","displayName":"CDT.cloud Clangd Contexts","description":"CDT.cloud - Support for multiple configuration contexts in clangd.","version":"0.9.0-next.4e06ecd.0","license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","publishConfig":{"access":"public"},"keywords":["cpp","clangd"],"dependencies":{"js-yaml":"^4.1.0"},"devDependencies":{"@types/chai-string":"^1.4.2","@types/js-yaml":"^4.0.2","@types/node":"~12","chai-string":"^1.5.0"},"scripts":{"clean":"rimraf lib *.tsbuildinfo && rimraf .eslintcache && rimraf .nyc_output coverage","lint":"if-env SKIP_LINT=true && echo 'skip lint check' || eslint --cache=true --no-error-on-unmatched-pattern=true \"{src,test}/**/*.{ts,tsx}\"","build":"tsc -b compile.tsconfig.json","test":"mocha --config ../../configs/mocharc.json \"./lib/**/*.*spec.js\""},"main":"lib/index","types":"lib/index","nyc":{"extends":"../../configs/nyc.json"},"gitHead":"4e06ecd7a1efa8758db89a2a21d70d5940965e10","readme":"# @eclipse-cdt-cloud/clangd-contexts\n\n## Overview\n\nAn API for management of [clangd](https://clangd.llvm.org) configuration files in C/C++ projects using _contexts_.\nA _context_ is the set of flags, parameters, other settings and source files that clangd uses as input.\nCurrently, this library is limited to configuring the compilation database (`compile_commands.json` file) and compile flags in the `.clangd` file for a project.\nContexts are identified via the names of the directories containing `compile_commands.json` files.\nIn the future additional settings may be associated with a specific context, for example the handling of additional or removed compilation flags (currently these are managed on an _ad hoc_ basis).\n\n## Features\n\n-   API for management of [clangd](https://clangd.llvm.org) configuration files\n-   retrieve and set contexts in one or more `.clangd` files\n-   manage compile flags in `.clangd` files\n\nThe API in the `clangd-config` and `clangd-context` modules manages the `CompileFlags` configuration of _clangd_ in the `.clangd` files in a C/C++ project.\nIn particular,\n\n-   which `CompilationDatabase` to use, referencing a `compile_commands.json` file\n-   any compiler flags to `Remove` from or `Add` to those specified in the compilation database when invoking `clang`\n\nThe API establishes two core concepts: a _project_ that is configured via a `.clangd` file and a _context_ that identifies a compilation database (a particular `compile_commands.json` file).\nA context's name is inferred from the name of the directory that contains the compilation database file.\nA workspace may have one or more projects each configured with a `.clangd` file for different subtrees.\nEach project has one or more contexts and in a multi-project workspace the projects' context names may overlap to any degree.\nThe [example workspace](../../examples/clangd-workspace/README.md) shows a fairly small example of how this can be laid out:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project\n  |   +-- Debug_x86-64/              // a \"Debug mode for x86-64 architecture\" context\n  |   |   +-- compile_commands.json  // the context's compilation database\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release_Atom/              // a \"Release mode for Atom architecture\" context\n  |   |   +-- compile_commands.json\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project\n      +-- Debug_x86-64/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- Release_Atom/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- .clangd                    // the clangd configuration for the \"lib\" project\n```\n\nThe core API for the `.clangd` configuration file does not assume any particular directory structure: client applications specify contexts to set into the `.clangd` file either by path to the `compile_commands.json` file or the directory containing it.\nThe inferred name of the context, which is useful primarily for presentation to the user in a UI or command-line tool, is the path name of the parent directory of the `compile_commands.json` file relative to the `.clangd` file for the project.\nSo, in the example above, the context names in both projects are \"Debug_x86-64\" and \"Release_Atom\".\n\nAnother API in the `clangd-contexts-config` module is provided to help clients discover existing projects and contexts of a workspace that is configured with an optional `.clangd-contexts` file that describes the layout of the workspace.\nA workspace may have one of these at the root or may have several `.clangd-contexts` files in different subtrees.\nA `.clangd-contexts` file enumerates the project directories in its scope and, for each, indicates whether context directories are organized in a flat list as in the example above or hierarchically as in the structure below:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project directory\n  |   +-- Debug/                     // \"Debug mode\" contexts\n  |   |   +-- x86-64/                // the \"Debug mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Debug mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release/                   // \"Release mode\" contexts\n  |   |   +-- x86-64/                // the \"Release mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Release mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project directory\n  |   +-- Debug/                     // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- Release/                   // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"lib\" project\n  +-- .clangd-contexts               // configuration of project layout in the workspace\n```\n\nThe API around the `.clangd-contexts` configuration file provides functions for querying what are the configured project directories and what are the\ndistinct context names available across all of those projects.\nIn this layout, the distinct context names are \"Debug/x86-64\", \"Debug/Atom\", \"Release/x86-64\", and \"Release/Atom\".\n\nCurrently, the `.clangd-contexts` file is limited to describing the shape of projects in the clangd workspace.\nA future enhancement should expand the configuration in this file to include lists of added/removed compile flags on a per project basis and, optionally, per context as well, allowing the `setContext` and `selectContext` APIs to update the added/removed compile flags in the `.clangd` configuration automatically on context switch.\n\n## Example Workspaces\n\n-   [`examples/clangd-workspace`](../../examples/clangd-workspace/README.md)\n    -   provides a small example workspace with two interrelated projects in which to test drive the API via the [VS Code Extension example](../../examples/clangd-contexts-ext/README.md) and/or the [CLI Example](../../examples/clangd-contexts-cli/README.md)\n\n## License\n\n-   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)\n-   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)\n","readmeFilename":"README.md","_id":"@eclipse-cdt-cloud/clangd-contexts@0.9.0-next.4e06ecd.0","_nodeVersion":"12.22.12","_npmVersion":"lerna/4.0.0/node@v12.22.12+x64 (linux)","dist":{"integrity":"sha512-ko96uNU5u8+sHjhGQ7mqM0a8broof3bo0Pp6LqLmsirg5BJm8Na++QID4V/AdjJOOB/3hPL3nzs4BkqBZh0miw==","shasum":"98d44ec24b340fa760e7c3a463396bc24710d713","tarball":"https://registry.npmjs.org/@eclipse-cdt-cloud/clangd-contexts/-/clangd-contexts-0.9.0-next.4e06ecd.0.tgz","fileCount":51,"unpackedSize":127988,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIGCHBYQ2GirniOY1n9rcGPWhFLBkElckSNvygtoP1Cg0AiBuYI+NqFfIFX4WwMnmw97WbnY3muXjRH3zPPv6bm/SBw=="}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjc8WdACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqFfQ/+KpeGDrESQJsiTY0BgwUywbSN6w/5F5Z1lY2aBkPhn+EfLNy9\r\nZwwnT2mrjTuhh4lKa4whICvuKxlmIu5ossmakH/avXtYT+uHaPySd3iYJjaJ\r\n9MroiABXzGNK3CG6OS4M38aPT2dAI2nk1ISlzgVi9HxcJDmG8GWs6/bdE/pv\r\naY1sI90ggmpCbRh3azU0IUT6VrN35jQCnKtngoVT3ZXNmXFCxwYwtozCeRG8\r\nrtbqhR+RbIiZPSuAlAwgZTtty9btRTm0gmL3UfjIAFFh4/Ywq3tJhhGnJRxV\r\n/oVckK0PAAarCUQ+bi13AF8ATJJ74I0r3uf7/d+pT90Xt27LKre6nnQUh/4k\r\ndwKMwiyvGaZbjJ8OEpbFdJX2owrYzfVUWSClxk1CwNaoEIMKEokNOJDexmd/\r\nlCS26DO3VYyk2i6smopuOW5sKv++o/YMFwfPUdALUzMrjpZ/kUeWSwKgksBP\r\nYWe+lcVDfGh2dKYhdS2HBPptqeO+pshfV1RSt62c9eIMt1LLyHxQgP89I3jL\r\nrPo6j9bVbqtBQsb0MnG8yKoZXKJPxJWgoyc7bgJYXD/CIUpSfumqFWOhqlzj\r\nvwy3nskgKNLjs1EnQGshbo6A5SEQZkwQKiI5G0E8bFpbJKx2io/1ZvKyNrUU\r\nDquO++4DLIJNACO60tUnY+gqMt7fEkz9mRs=\r\n=cvfS\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},"directories":{},"maintainers":[{"name":"jonahgraham","email":"jonah@kichwacoders.com"},{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/clangd-contexts_0.9.0-next.4e06ecd.0_1668531612844_0.3922810457538266"},"_hasShrinkwrap":false},"0.9.0-next.b9f338c.0":{"name":"@eclipse-cdt-cloud/clangd-contexts","displayName":"CDT.cloud Clangd Contexts","description":"CDT.cloud - Support for multiple configuration contexts in clangd.","version":"0.9.0-next.b9f338c.0","license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","publishConfig":{"access":"public"},"keywords":["cpp","clangd"],"dependencies":{"js-yaml":"^4.1.0"},"devDependencies":{"@types/chai-string":"^1.4.2","@types/js-yaml":"^4.0.2","@types/mkdirp":"^1.0.2","@types/node":"14.x","chai-string":"^1.5.0"},"scripts":{"clean":"rimraf lib *.tsbuildinfo && rimraf .eslintcache && rimraf .nyc_output coverage","lint":"if-env SKIP_LINT=true && echo 'skip lint check' || eslint --cache=true --no-error-on-unmatched-pattern=true \"{src,test}/**/*.{ts,tsx}\"","build":"tsc -b compile.tsconfig.json","test":"mocha --config ../../configs/mocharc.json \"./lib/**/*.*spec.js\""},"main":"lib/index","types":"lib/index","nyc":{"extends":"../../configs/nyc.json"},"gitHead":"b9f338ceb2b49b841553998ad2e6ad307a11f0c1","readme":"# @eclipse-cdt-cloud/clangd-contexts\n\n## Overview\n\nAn API for management of [clangd](https://clangd.llvm.org) configuration files in C/C++ projects using _contexts_.\nA _context_ is the set of flags, parameters, other settings and source files that clangd uses as input.\nCurrently, this library is limited to configuring the compilation database (`compile_commands.json` file) and compile flags in the `.clangd` file for a project.\nContexts are identified via the names of the directories containing `compile_commands.json` files.\nIn the future additional settings may be associated with a specific context, for example the handling of additional or removed compilation flags (currently these are managed on an _ad hoc_ basis).\n\n## Features\n\n-   API for management of [clangd](https://clangd.llvm.org) configuration files\n-   retrieve and set contexts in one or more `.clangd` files\n-   manage compile flags in `.clangd` files\n\nThe API in the `clangd-config` and `clangd-context` modules manages the `CompileFlags` configuration of _clangd_ in the `.clangd` files in a C/C++ project.\nIn particular,\n\n-   which `CompilationDatabase` to use, referencing a `compile_commands.json` file\n-   any compiler flags to `Remove` from or `Add` to those specified in the compilation database when invoking `clang`\n\nThe API establishes two core concepts: a _project_ that is configured via a `.clangd` file and a _context_ that identifies a compilation database (a particular `compile_commands.json` file).\nA context's name is inferred from the name of the directory that contains the compilation database file.\nA workspace may have one or more projects each configured with a `.clangd` file for different subtrees.\nEach project has one or more contexts and in a multi-project workspace the projects' context names may overlap to any degree.\nThe [example workspace](../../examples/clangd-workspace/README.md) shows a fairly small example of how this can be laid out:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project\n  |   +-- Debug_x86-64/              // a \"Debug mode for x86-64 architecture\" context\n  |   |   +-- compile_commands.json  // the context's compilation database\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release_Atom/              // a \"Release mode for Atom architecture\" context\n  |   |   +-- compile_commands.json\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project\n      +-- Debug_x86-64/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- Release_Atom/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- .clangd                    // the clangd configuration for the \"lib\" project\n```\n\nThe core API for the `.clangd` configuration file does not assume any particular directory structure: client applications specify contexts to set into the `.clangd` file either by path to the `compile_commands.json` file or the directory containing it.\nThe inferred name of the context, which is useful primarily for presentation to the user in a UI or command-line tool, is the path name of the parent directory of the `compile_commands.json` file relative to the `.clangd` file for the project.\nSo, in the example above, the context names in both projects are \"Debug_x86-64\" and \"Release_Atom\".\n\nAnother API in the `clangd-contexts-config` module is provided to help clients discover existing projects and contexts of a workspace that is configured with an optional `.clangd-contexts` file that describes the layout of the workspace.\nA workspace may have one of these at the root or may have several `.clangd-contexts` files in different subtrees.\nA `.clangd-contexts` file enumerates the project directories in its scope and, for each, indicates whether context directories are organized in a flat list as in the example above or hierarchically as in the structure below:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project directory\n  |   +-- Debug/                     // \"Debug mode\" contexts\n  |   |   +-- x86-64/                // the \"Debug mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Debug mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release/                   // \"Release mode\" contexts\n  |   |   +-- x86-64/                // the \"Release mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Release mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project directory\n  |   +-- Debug/                     // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- Release/                   // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"lib\" project\n  +-- .clangd-contexts               // configuration of project layout in the workspace\n```\n\nThe API around the `.clangd-contexts` configuration file provides functions for querying what are the configured project directories and what are the\ndistinct context names available across all of those projects.\nIn this layout, the distinct context names are \"Debug/x86-64\", \"Debug/Atom\", \"Release/x86-64\", and \"Release/Atom\".\n\nCurrently, the `.clangd-contexts` file is limited to describing the shape of projects in the clangd workspace.\nA future enhancement should expand the configuration in this file to include lists of added/removed compile flags on a per project basis and, optionally, per context as well, allowing the `setContext` and `selectContext` APIs to update the added/removed compile flags in the `.clangd` configuration automatically on context switch.\n\n## Example Workspaces\n\n-   [`examples/clangd-workspace`](../../examples/clangd-workspace/README.md)\n    -   provides a small example workspace with two interrelated projects in which to test drive the API via the [VS Code Extension example](../../examples/clangd-contexts-ext/README.md) and/or the [CLI Example](../../examples/clangd-contexts-cli/README.md)\n\n## License\n\n-   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)\n-   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)\n","readmeFilename":"README.md","_id":"@eclipse-cdt-cloud/clangd-contexts@0.9.0-next.b9f338c.0","_nodeVersion":"16.18.1","_npmVersion":"lerna/6.0.3/node@v16.18.1+x64 (linux)","dist":{"integrity":"sha512-hxeOuvaeF8/8Qtdm44UUKFgWrlB9bpiszBxD1K0fYx6MW7RJdvXxOBXMynZ7nhrdjzyQ/DFej+PUpjX9l+26/A==","shasum":"d3bcfa223fd7bf1da17611979d4d93712c0c85bc","tarball":"https://registry.npmjs.org/@eclipse-cdt-cloud/clangd-contexts/-/clangd-contexts-0.9.0-next.b9f338c.0.tgz","fileCount":51,"unpackedSize":130092,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDIC0cTOW0fKG0u5vLfl9BRjENc4Qcfpc7RNkYAjy10YwIhAIBHTMJArLJpMzcV6GaBIRU7s+eez6NOsFSKdIa1pRZP"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJjnDd6ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmruqQ//ZzPS3t8B1jeiD/ire1o3OPoiHVFEjwSV0R77tuPgzW6iNqKS\r\nml2U/DgDvgBaNuZWDhQH/UR4JTxTzO8bpMPOATDqFzaHmMZxpXuGhfthn5lB\r\nwC9Do0Mki2W2XT3dETW8VxYllXZk+rdBR2owtPfY7nHPBElAx104Bj07EUkR\r\nRza3z5zh5nY+7orPsR2NTlo6h5GDvrQyK/S9sRTP9FBrhCmfO6wj+NZFG6Ev\r\nc8VMzsAwykVfG+s9C5ptZ/nCxsK4r3e7tQcoFxJOYxtHj5Xbcmw3Uy2jicW7\r\npsibePUnhVWpFmG3DdgqUuwzti9dOooWrWqa6l7iurY9mHfOAxGiDZYmrJcU\r\n7GTkXvnrqGQ9kUgGiQDhcRGRlhJbD4QQbcbJ8BFffg3Clb6YjxuKprM8vR9x\r\nm37OcB5dTz35Twu8r/5J+EFRJYr462qhDiU+vpkI2cu3P6TuRMWLK1hB+Ki2\r\nDFswnRf2u1ZQpqRf42GKxQUzKk3XJiSpTQ2c1/2FeiUEoWWZYg3wr6A27Ksp\r\ntmNYkpvwoxElF2qLu8bRnXmS2/nKQSJKHL04fAz4KAgismndlXLVoqCcgzdm\r\naSpHCfonc7c+J9GN4lpXL8kXokA6S5BrdAlUUsFt7s0hdbmCHVycaHBfGG7p\r\nveZQo5Bo62zkMQ7Zm+ckMAmpffgsopHGLzc=\r\n=D8Hy\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},"directories":{},"maintainers":[{"name":"jonahgraham","email":"jonah@kichwacoders.com"},{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/clangd-contexts_0.9.0-next.b9f338c.0_1671182202624_0.7208947173587228"},"_hasShrinkwrap":false},"0.9.0-next.48df6c3.0":{"name":"@eclipse-cdt-cloud/clangd-contexts","displayName":"CDT.cloud Clangd Contexts","description":"CDT.cloud - Support for multiple configuration contexts in clangd.","version":"0.9.0-next.48df6c3.0","license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","publishConfig":{"access":"public"},"keywords":["cpp","clangd"],"dependencies":{"js-yaml":"^4.1.0"},"devDependencies":{"@types/chai-string":"^1.4.2","@types/js-yaml":"^4.0.2","@types/mkdirp":"^1.0.2","@types/node":"14.x","chai-string":"^1.5.0"},"scripts":{"clean":"rimraf lib *.tsbuildinfo && rimraf .eslintcache && rimraf .nyc_output coverage","lint":"if-env SKIP_LINT=true && echo 'skip lint check' || eslint --cache=true --no-error-on-unmatched-pattern=true \"{src,test}/**/*.{ts,tsx}\"","build":"tsc -b compile.tsconfig.json","test":"mocha --config ../../configs/mocharc.json \"./lib/**/*.*spec.js\""},"main":"lib/index","types":"lib/index","nyc":{"extends":"../../configs/nyc.json"},"gitHead":"48df6c3182296c9be9a1c8095426d5420b6a5bab","readme":"# @eclipse-cdt-cloud/clangd-contexts\n\n## Overview\n\nAn API for management of [clangd](https://clangd.llvm.org) configuration files in C/C++ projects using _contexts_.\nA _context_ is the set of flags, parameters, other settings and source files that clangd uses as input.\nCurrently, this library is limited to configuring the compilation database (`compile_commands.json` file) and compile flags in the `.clangd` file for a project.\nContexts are identified via the names of the directories containing `compile_commands.json` files.\nIn the future additional settings may be associated with a specific context, for example the handling of additional or removed compilation flags (currently these are managed on an _ad hoc_ basis).\n\n## Features\n\n-   API for management of [clangd](https://clangd.llvm.org) configuration files\n-   retrieve and set contexts in one or more `.clangd` files\n-   manage compile flags in `.clangd` files\n\nThe API in the `clangd-config` and `clangd-context` modules manages the `CompileFlags` configuration of _clangd_ in the `.clangd` files in a C/C++ project.\nIn particular,\n\n-   which `CompilationDatabase` to use, referencing a `compile_commands.json` file\n-   any compiler flags to `Remove` from or `Add` to those specified in the compilation database when invoking `clang`\n\nThe API establishes two core concepts: a _project_ that is configured via a `.clangd` file and a _context_ that identifies a compilation database (a particular `compile_commands.json` file).\nA context's name is inferred from the name of the directory that contains the compilation database file.\nA workspace may have one or more projects each configured with a `.clangd` file for different subtrees.\nEach project has one or more contexts and in a multi-project workspace the projects' context names may overlap to any degree.\nThe [example workspace](../../examples/clangd-workspace/README.md) shows a fairly small example of how this can be laid out:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project\n  |   +-- Debug_x86-64/              // a \"Debug mode for x86-64 architecture\" context\n  |   |   +-- compile_commands.json  // the context's compilation database\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release_Atom/              // a \"Release mode for Atom architecture\" context\n  |   |   +-- compile_commands.json\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project\n      +-- Debug_x86-64/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- Release_Atom/              // similar context as in the \"app\" project\n      |   +-- compile_commands.json\n      |   +-- ...\n      +-- .clangd                    // the clangd configuration for the \"lib\" project\n```\n\nThe core API for the `.clangd` configuration file does not assume any particular directory structure: client applications specify contexts to set into the `.clangd` file either by path to the `compile_commands.json` file or the directory containing it.\nThe inferred name of the context, which is useful primarily for presentation to the user in a UI or command-line tool, is the path name of the parent directory of the `compile_commands.json` file relative to the `.clangd` file for the project.\nSo, in the example above, the context names in both projects are \"Debug_x86-64\" and \"Release_Atom\".\n\nAnother API in the `clangd-contexts-config` module is provided to help clients discover existing projects and contexts of a workspace that is configured with an optional `.clangd-contexts` file that describes the layout of the workspace.\nA workspace may have one of these at the root or may have several `.clangd-contexts` files in different subtrees.\nA `.clangd-contexts` file enumerates the project directories in its scope and, for each, indicates whether context directories are organized in a flat list as in the example above or hierarchically as in the structure below:\n\n```plain\nworkspace/                           // a multi-project workspace\n  +-- app/                           // a project directory\n  |   +-- Debug/                     // \"Debug mode\" contexts\n  |   |   +-- x86-64/                // the \"Debug mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Debug mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- Release/                   // \"Release mode\" contexts\n  |   |   +-- x86-64/                // the \"Release mode\" context for x86-64 architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Atom/                  // the \"Release mode\" context for Atom architecture\n  |   |   |   +-- compile_commands.json\n  |   |   |   +-- Makefile\n  |   |   |   +-- ...\n  |   |   +-- Makefile\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"app\" project\n  +-- lib/                           // another project directory\n  |   +-- Debug/                     // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- Release/                   // similar context as in the \"app\" project\n  |   |   +-- x86-64/\n  |   |   +-- Atom/\n  |   |   +-- ...\n  |   +-- .clangd                    // the clangd configuration for the \"lib\" project\n  +-- .clangd-contexts               // configuration of project layout in the workspace\n```\n\nThe API around the `.clangd-contexts` configuration file provides functions for querying what are the configured project directories and what are the\ndistinct context names available across all of those projects.\nIn this layout, the distinct context names are \"Debug/x86-64\", \"Debug/Atom\", \"Release/x86-64\", and \"Release/Atom\".\n\nCurrently, the `.clangd-contexts` file is limited to describing the shape of projects in the clangd workspace.\nA future enhancement should expand the configuration in this file to include lists of added/removed compile flags on a per project basis and, optionally, per context as well, allowing the `setContext` and `selectContext` APIs to update the added/removed compile flags in the `.clangd` configuration automatically on context switch.\n\n## Example Workspaces\n\n-   [`examples/clangd-workspace`](../../examples/clangd-workspace/README.md)\n    -   provides a small example workspace with two interrelated projects in which to test drive the API via the [VS Code Extension example](../../examples/clangd-contexts-ext/README.md) and/or the [CLI Example](../../examples/clangd-contexts-cli/README.md)\n\n## License\n\n-   [Eclipse Public License 2.0](http://www.eclipse.org/legal/epl-2.0/)\n-   [一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception](https://projects.eclipse.org/license/secondary-gpl-2.0-cp)\n","readmeFilename":"README.md","_id":"@eclipse-cdt-cloud/clangd-contexts@0.9.0-next.48df6c3.0","_nodeVersion":"16.19.0","_npmVersion":"lerna/6.0.3/node@v16.19.0+x64 (linux)","dist":{"integrity":"sha512-KhbWkpNFaO1khDvAbQb+oN5z5vonPGU66cMxwD57E5NHZ1UMZy3QnrBTrN9oW5dWpJeRXyuX+vHXxeqg1oy1ww==","shasum":"4bc2936bd90d376e7a56de857d4432d75d51b493","tarball":"https://registry.npmjs.org/@eclipse-cdt-cloud/clangd-contexts/-/clangd-contexts-0.9.0-next.48df6c3.0.tgz","fileCount":51,"unpackedSize":130092,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCyifAijAiColzCmMxZJMZpwQpR9dzmTrzD+fcmk+ncLAIgGTXf5MT1Hly8MUNIBAPLkbn58RETZs1w9kTtRS1Yn6U="}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJj7eaMACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmo2LBAAhecWMleJX4NS/6CkkOAEZL6EKmhgUFlhxcm/FGQLbI6EitvK\r\noYzqwS6CooVCIvuaraQhs+AlL+xBtZG6qnSJ4fk0aXfHTwjFfMk4UoX20QgN\r\nJV2Lj7QPIcOqKB1SlB/i/oVlV7E5dWF5SRwDptpU6fihnLWKKpSY43yqLYC9\r\nhl1akkFsoWxRpCnRfsQdOHThVBMbUAo2YRl7/XLavxtaTuAzQ7n15s9gEuzH\r\nj8iE58kWHL2uvEjbEuxwWqHSD5jloLmO0bY3V3pg9i2bAU3scb4ONE6KIMij\r\n7NK8xZLnQp5OiuOHO7MZteIDVzVe2djy8RnnhrI5Bo+MVTCgBGzOZChaQlTt\r\nWLw0CahYToU+ts3RRG8eIVai2HpydjeRGOKbL5qDXG0d1OlekedJxFD+DgYr\r\n4Bk0IU+D+CUcbNybmoPqaiVfGYFOr+nf8dK3hN5J5tAN6fWThy3MduPvVCyA\r\nYsVZMrO6Z0+rgq3ZKkD0yQXf1vkRuTTSJl1iN2BeGWYOr74EoR6oHizjeook\r\nl4CHtChnPyS6lS/W11QT79/+GCc6V+wdtrjfARGGadVXgOG1bcqYyJ52sUnO\r\nijX33UFhkvfdXhIU6wZKFFxeHvROJIRpgGCgtMAxqS23Pd9gRCpmgeOPe5ql\r\n6ev33ltV4VzqUIKtzj3QoBRsxeE3d8z3X74=\r\n=HHff\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},"directories":{},"maintainers":[{"name":"jonahgraham","email":"jonah@kichwacoders.com"},{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/clangd-contexts_0.9.0-next.48df6c3.0_1676535436339_0.8647803792529778"},"_hasShrinkwrap":false}},"time":{"created":"2022-02-17T13:08:06.010Z","0.9.0-next.c7c35a6.0":"2022-02-17T13:08:06.249Z","modified":"2023-02-16T08:17:16.654Z","0.9.0-next.47b67f9.0":"2022-02-17T13:26:08.214Z","0.9.0-next.4e06ecd.0":"2022-11-15T17:00:13.018Z","0.9.0-next.b9f338c.0":"2022-12-16T09:16:42.781Z","0.9.0-next.48df6c3.0":"2023-02-16T08:17:16.515Z"},"maintainers":[{"name":"jonahgraham","email":"jonah@kichwacoders.com"},{"name":"eclipse-cdt-cloud-bot","email":"cdt-cloud-bot@eclipse.org"},{"name":"planger","email":"planger@eclipsesource.com"}],"description":"CDT.cloud - Support for multiple configuration contexts in clangd.","keywords":["cpp","clangd"],"license":"EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0","readme":"","readmeFilename":""}