@chauvet/connect-base-profiles 1.0.0 → 1.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,68 @@
1
+ ## Versioning & Publishing
2
+
3
+ ### 1. Log in to npm
4
+
5
+ You must be logged into npm with the appropriate account before publishing:
6
+
7
+ ```bash
8
+ npm login
9
+ ```
10
+
11
+ After entering your credentials, verify your login status:
12
+
13
+ ```bash
14
+ npm whoami
15
+ ```
16
+
17
+ This should display your username. If you’re not recognized, repeat the npm login step or check your credentials.
18
+
19
+ ---
20
+
21
+ ### 2. Determine the Version Bump
22
+ We follow Semantic Versioning. Here’s the convention for deciding which part of the version number to increment:
23
+
24
+ - **Patch**: For small corrections and bug fixes (no changes to the data structure or feature set).
25
+ - **Minor**: For adding new fixtures or functionality (in a backward-compatible manner).
26
+ - **Major**: For any breaking changes to the data structure or how consumers use this library.
27
+ Use the appropriate command to bump the version:
28
+
29
+ ```bash
30
+ # For a patch release (e.g., 1.0.0 → 1.0.1):
31
+ npm version patch
32
+
33
+ # For a minor release (e.g., 1.0.1 → 1.1.0):
34
+ npm version minor
35
+
36
+ # For a major release (e.g., 1.1.0 → 2.0.0):
37
+ npm version major
38
+ ```
39
+
40
+ This will automatically update your package.json, create a Git commit, and tag it with the new version.
41
+
42
+ ---
43
+ ### 3. Push Your Changes and Tags
44
+ If the version command didn’t automatically push your commit and tag, do so now:
45
+
46
+ ```bash
47
+ git push
48
+ git push --tags
49
+ ```
50
+
51
+ ---
52
+ ### 4. Publish to npm
53
+ Finally, publish your changes. If your package is scoped and intended to be publicly available, use:
54
+
55
+ ```bash
56
+ npm publish --access public
57
+ ```
58
+
59
+ ---
60
+ ### 5. Verify
61
+ Check the published version on npm:
62
+
63
+ ```bash
64
+ npm info @chauvet/connect-base-profiles
65
+ ```
66
+
67
+ You should see the newly published version in the output. If everything looks good, your updated package is now available for others to install.
68
+
package/package.json CHANGED
@@ -1,11 +1,17 @@
1
1
  {
2
2
  "name": "@chauvet/connect-base-profiles",
3
- "version": "1.0.0",
3
+ "version": "1.2.0",
4
4
  "type": "module",
5
5
  "main": "dist/baseProfiles.js",
6
6
  "types": "dist/baseProfiles.d.ts",
7
7
  "scripts": {
8
- "build": "tsc"
8
+ "build": "tsc",
9
+ "bump:version": "bash -c 'if [ -z \"$1\" ]; then echo \"❌ Please provide a version: npm run bump:version -- 1.5.0\"; exit 1; else npm version --no-git-tag-version \"$1\"; fi' -",
10
+ "bump:patch": "npm version patch --no-git-tag-version",
11
+ "bump:minor": "npm version minor --no-git-tag-version",
12
+ "bump:major": "npm version major --no-git-tag-version",
13
+ "publish": " npm publish --access public",
14
+ "check": "npm info @chauvet/connect-base-profiles"
9
15
  },
10
16
  "keywords": [],
11
17
  "author": "",
@@ -29,22 +29,12 @@ const baseProfiles: Record<number, BaseProfile> = {
29
29
  },
30
30
  whiteLocation: 0,
31
31
  amberLocation: 5,
32
- whiteMacrosLocation: 7,
32
+ whiteMacrosLocation: 0,
33
33
  uvLocation: 0,
34
34
  dimmerLocation: 1,
35
35
  fineDimmerLocation: 0,
36
36
  strobeLocation: 6,
37
- whiteMacros: {
38
- '2800': 6,
39
- '3200': 26,
40
- '3500': 51,
41
- '4000': 76,
42
- '4500': 101,
43
- '5000': 126,
44
- '5600': 151,
45
- '6000': 176,
46
- '6500': 201,
47
- },
37
+ whiteMacros: {},
48
38
  name: 'WELL FIT',
49
39
  },
50
40
  60: {
@@ -1,8 +0,0 @@
1
- <?xml version="1.0" encoding="UTF-8"?>
2
- <module type="WEB_MODULE" version="4">
3
- <component name="NewModuleRootManager">
4
- <content url="file://$MODULE_DIR$" />
5
- <orderEntry type="inheritedJdk" />
6
- <orderEntry type="sourceFolder" forTests="false" />
7
- </component>
8
- </module>
package/.idea/modules.xml DELETED
@@ -1,8 +0,0 @@
1
- <?xml version="1.0" encoding="UTF-8"?>
2
- <project version="4">
3
- <component name="ProjectModuleManager">
4
- <modules>
5
- <module fileurl="file://$PROJECT_DIR$/.idea/base-profiles.iml" filepath="$PROJECT_DIR$/.idea/base-profiles.iml" />
6
- </modules>
7
- </component>
8
- </project>
package/.idea/php.xml DELETED
@@ -1,19 +0,0 @@
1
- <?xml version="1.0" encoding="UTF-8"?>
2
- <project version="4">
3
- <component name="MessDetectorOptionsConfiguration">
4
- <option name="transferred" value="true" />
5
- </component>
6
- <component name="PHPCSFixerOptionsConfiguration">
7
- <option name="transferred" value="true" />
8
- </component>
9
- <component name="PHPCodeSnifferOptionsConfiguration">
10
- <option name="highlightLevel" value="WARNING" />
11
- <option name="transferred" value="true" />
12
- </component>
13
- <component name="PhpStanOptionsConfiguration">
14
- <option name="transferred" value="true" />
15
- </component>
16
- <component name="PsalmOptionsConfiguration">
17
- <option name="transferred" value="true" />
18
- </component>
19
- </project>