From da6fc63cd4ec850aec59500bcc3775e515b03b52 Mon Sep 17 00:00:00 2001 From: Alok Kumar Date: Tue, 5 Nov 2024 11:21:18 +0530 Subject: [PATCH] updated Signed-off-by: Alok Kumar --- docs/source/matchcode/matchcode-pipeline.rst | 5 +++-- package-lock.json | 6 ++++++ 2 files changed, 9 insertions(+), 2 deletions(-) create mode 100644 package-lock.json diff --git a/docs/source/matchcode/matchcode-pipeline.rst b/docs/source/matchcode/matchcode-pipeline.rst index 075671fe..b8a16ec2 100644 --- a/docs/source/matchcode/matchcode-pipeline.rst +++ b/docs/source/matchcode/matchcode-pipeline.rst @@ -4,11 +4,12 @@ Code Matching The aim of this tutorial is to show how to use the MatchCode.io API to perform code matching on an archive of files. + .. note:: This tutorial assumes that you have a working installation of PurlDB. If you don't, please refer to the `installation - <../purldb/overview.html#installation>`_ page. - + `_ + page. Throughout this tutorial, we will use ``pkg:npm/deep-equal@1.0.1`` and a modified copy of ``index.js`` from it. diff --git a/package-lock.json b/package-lock.json new file mode 100644 index 00000000..affa347f --- /dev/null +++ b/package-lock.json @@ -0,0 +1,6 @@ +{ + "name": "purldb", + "lockfileVersion": 3, + "requires": true, + "packages": {} +}