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
* The url to your project’s issue tracker and / or the email address to which issues should be reported. These are helpful for people who encounter issues with your package.
34
34
*/
35
35
bugs?:
36
-
|string
37
-
|{
38
-
url?: string;
39
-
email?: string;
40
-
};
36
+
|string
37
+
|{
38
+
url?: string;
39
+
email?: string;
40
+
};
41
41
42
42
/**
43
43
* You should specify a license for your package so that people know how they are permitted to use it, and any restrictions you’re placing on it.
* For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same shortcut syntax you use for npm install:
50
50
*/
51
51
repository?:
52
-
|string
53
-
|{
54
-
type: string;
55
-
url: string;
56
-
/**
57
-
* If the `package.json` for your package is not in the root directory (for example if it is part of a monorepo), you can specify the directory in which it lives:
58
-
*/
59
-
directory?: string;
60
-
};
52
+
|string
53
+
|{
54
+
type: string;
55
+
url: string;
56
+
/**
57
+
* If the `package.json` for your package is not in the root directory (for example if it is part of a monorepo), you can specify the directory in which it lives:
58
+
*/
59
+
directory?: string;
60
+
};
61
61
62
62
/**
63
63
* The `scripts` field is a dictionary containing script commands that are run at various times in the lifecycle of your package.
0 commit comments