You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to verify the license checks for the builtin extensions, some extra steps were required to do so since such plugins are not hoisted to the repository's node_modules. The steps were to walk through the available extensions under vscode/extensions in order to obtain the list of package.json and collect their dependencies. These dependencies were then added to a package.json which was built, and generated a package.lock.json which was used in Clearly Defined. The goal is to eventually automate this process better and productify it so we can re-use it in the future if need be.
Description
In order to verify the license checks for the
builtin
extensions, some extra steps were required to do so since such plugins are not hoisted to the repository'snode_modules
. The steps were to walk through the available extensions undervscode/extensions
in order to obtain the list ofpackage.json
and collect theirdependencies
. These dependencies were then added to apackage.json
which was built, and generated apackage.lock.json
which was used in Clearly Defined. The goal is to eventually automate this process better and productify it so we can re-use it in the future if need be.The current steps:
yarn
)cd extensions
used to iterate over the available
package.json
under a directory and collect the dependenciespackage-deps -d **package.json > dependencies.txt
npm init -y
dependencies.txt
to the new package.jsonnpm i
(installs dependencies and generates apackage.lock.json
)package.lock.json
to clearly defined and verify for any invalid licensesThe text was updated successfully, but these errors were encountered: