devcleaner 0.1.2

A tool to search for node_modules an clean the projects selected
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

<?xml version="1.0" encoding="utf-8"?>
<!-- Read this before creating packages: https://chocolatey.org/docs/create-packages -->
<!-- It is especially important to read the above link to understand additional requirements when publishing packages to the community feed aka dot org (https://chocolatey.org/packages). -->

<!-- Test your packages in a test environment: https://github.com/chocolatey/chocolatey-test-environment -->

<!--
This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Reference. Chocolatey uses a special version of NuGet.Core that allows us to do more than was initially possible. As such there are certain things to be aware of:

* the package xmlns schema url may cause issues with nuget.exe
* Any of the following elements can ONLY be used by choco tools - projectSourceUrl, docsUrl, mailingListUrl, bugTrackerUrl, packageSourceUrl, provides, conflicts, replaces 
* nuget.exe can still install packages with those elements but they are ignored. Any authoring tools or commands will error on those elements 
-->

<!-- You can embed software files directly into packages, as long as you are not bound by distribution rights. -->
<!-- * If you are an organization making private packages, you probably have no issues here -->
<!-- * If you are releasing to the community feed, you need to consider distribution rights. -->
<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
  <metadata>
    <!-- == PACKAGE SPECIFIC SECTION == -->
    <id>devcleaner</id>
    <version>$version</version>

    <!-- == SOFTWARE SPECIFIC SECTION == -->
    <!-- This section is about the software itself -->
    <title>DevCleaner</title>
    <authors>Yuniel Acosta Pérez</authors>
    <projectUrl>https://github.com/DevCleaner/devcleaner</projectUrl>
    <licenseUrl>https://github.com/DevCleaner/devcleaner/blob/main/LICENSE</licenseUrl>
    <requireLicenseAcceptance>true</requireLicenseAcceptance>
    <projectSourceUrl>https://github.com/DevCleaner/devcleaner</projectSourceUrl>
    <docsUrl>https://github.com/DevCleaner/devcleaner/blob/main/README.md</docsUrl>
    <bugTrackerUrl>https://github.com/DevCleaner/devcleaner/issues</bugTrackerUrl>
    <tags>cli cross-platform terminal npm devcleaner node node_modules cleaner rust</tags>
    <summary>A tool to search for node_modules an clean the projects selected</summary>
    <description>
    A tool to search for node_modules an clean the projects selected

    **Usage**
    To use, run `devcleaner` in a terminal.
    
    For more [documentation and usage](https://github.com/DevCleaner/devcleaner/blob/main/README.md), see the [official repo](https://github.com/DevCleaner/devcleaner).
    
    </description>
    <releaseNotes>https://github.com/DevCleaner/devcleaner/releases/tag/v$version/</releaseNotes>
  </metadata>
  <files>
    <!-- this section controls what actually gets packaged into the Chocolatey package -->
    <file src="tools\**" target="tools" />
    <!--Building from Linux? You may need this instead: <file src="tools/**" target="tools" />-->
  </files>
</package>