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
## <aname="setup"></a> Setting up your Environment
29
+
30
+
To set up your environment to work on angular-split, follow these steps:
31
+
32
+
1.**Fork the repository** on GitHub to your own account.
33
+
2.**Clone the repository** to your local machine
34
+
3.**Install the dependencies**: `npm install`
35
+
36
+
> Note: If you are using a version of Node.js that is not supported by angular-split, you might need to use `nvm` (Node Version Manager) to switch to a compatible version. The recommended version is Node.js 22.x LTS or later.
37
+
38
+
4.**build and run the project by**: `npm run start --watch`
39
+
40
+
For windows users, we expect you to use the WSL, as we set up the project to work with github actions. Make sure to check out the project and run the commands in the WSL terminal.
41
+
It might work outside the WSL when you delete the `package-lock.json` file, but we cannot guarantee that it will work. (also, make sure you don't commit that `package-lock.json`, as it will break the build for other users).
13
42
14
43
## <aname="coc"></a> Code of Conduct
15
44
@@ -190,7 +219,7 @@ Must be one of the following:
190
219
The scope should be the name of the module affected as perceived by the person reading changelog generated from the commit messages.
191
220
192
221
The following is the list of supported scopes (there might be more added in the fututre):
193
-
222
+
194
223
## TODO
195
224
196
225
There are currently a few exceptions to the "use package name" rule:
0 commit comments