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
$ npm i carbon-components-angular carbon-components
10
+
$ # include carbon css
11
+
$ # import components
12
+
$ npm start
14
13
```
15
-
</a>
16
-
17
-
Follow instructions in [Neutrino Seed repo](https://github.ibm.com/peretz/neutrino-seed) and use the rest of this readme if you need more detailed information.
3) on the *set me up* card, type 'peretz' into the search box
46
-
4) click on wce-peretz-npm-local
47
-
5) A dialog will appear, in that Add your credentials at the top right corner
48
-
6) Inside the same dialog, there is a section _using basic authentication_ copy and paste the same info in your `.npmrc` file _(in Windows `%USERPROFILE%/.npmrc`)_
49
-
7) save your changes and try npm update
50
-
51
-
##### Getting errors?
52
-
53
-
If you recently changed you w3id password, you'll get an error like `npm ERR! 403 Forbidden: @peretz/neutrino@...` and you will have to update your `~/.npmrc` by retaking the "Artifactory" step. Remove references to `peretz` from it before, or delete the whole file if you can (i.e. if peretz libraries are only thing you use from artifactory).
54
14
55
15
#### Bundler
56
16
@@ -72,7 +32,7 @@ Then you'll be able to `npm install @peretz/neutrino` and `npm install @peretz/m
72
32
-**if you are contributing a fix**:
73
33
- add your fix, update the documentation as needed
74
34
- consider adding or modifying a test case to cover the fix
75
-
- follow the [Neutrino style guide](https://github.ibm.com/peretz/neutrino/wiki/Style-guide), [Angular style guide](https://angular.io/styleguide) and [our general component guidelines](https://github.ibm.com/peretz/neutrino/wiki/General-component-API-guidelines)
35
+
- follow the [Angular style guide](https://angular.io/styleguide)
76
36
- be sure to run `npm test` and `npm run lint` to make sure the tests and linter pass
77
37
- DO NOT change the version number.
78
38
- submit a PR
@@ -101,30 +61,27 @@ Then you'll be able to `npm install @peretz/neutrino` and `npm install @peretz/m
101
61
- current behaviour
102
62
- screenshots if needed
103
63
- relevant code snippets
104
-
- links to application source code or running demo (including connection/authentication information)
64
+
- links to application source code or running demo ([Codesandbox is awesome for this!](https://codesandbox.io/s/angular)) (including connection/authentication information)
- if you have a fix to contribute, assign yourself, otherwise leave unassigned
107
67
108
68
#### npm commands
109
-
To keep our build dependancies local we use npm scripts to run our webpack, gulp, and general build tasks. You should never install webpack or gulp globally as that will likely conflict with our version. You should never need to modify the build process to add a component or demo.
110
-
-`npm run demo:server` to run the demo server (port 9000)
111
-
-`npm run demo:build` to build the demo
69
+
To keep our build dependancies local we use npm scripts to run our webpack, gulp, and general build tasks. You should never install webpack or gulp globally as that will likely conflict with our version. You should never need to modify the build process to add a component or story.
70
+
-`npm run storybook` to run storybook (port 6006)
112
71
-`npm run build` to generate the dist
113
72
-`docs:build` to build documentation
114
73
-`docs:server` to build and run the documentation server
-[Dynamic Assessment Plugin (aka. DAP/RPT)](https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W88ee03f8907c_412b_a3a8_988dabb72b35/page/Dynamic%20Assessment%20Plugin) - now shipping a pretty solid chrome plugin
127
-
-[CDL Icon Library](https://icon.stage1.mybluemix.net/) - Note only the icons in the "MASTER SET" sets are maintained
84
+
128
85
129
86
### Philosophy
130
87
- Components should be the smallest unit of computation
@@ -137,8 +94,3 @@ To keep our build dependancies local we use npm scripts to run our webpack, gulp
137
94
- Likewise, stateless components should be favored whenever possible
138
95
- Components should NOT *necessarily* implement the style guide point-for-point, the guide simply provides guidance on overarching functionality, components should enable that and product specific designs **without** baking in extra functionality
0 commit comments