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
Copy file name to clipboardExpand all lines: README.md
+11-14Lines changed: 11 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,37 +22,34 @@ Make sure you are running your terminal/command line session as administrator. T
22
22
23
23
### Choose Your Adventure! Now Vanilla, Grunt & Gulp
24
24
25
-
This repository ships with two `package.json` files, a `Gruntfile.js`, and a `gulpfile.js`. The default is grunt currently. The core builder is not dependent on either.
25
+
This repository ships a `Gruntfile.js`, and a `gulpfile.js`. The default is grunt currently. The core builder and tests are not dependent on either.
26
26
27
27
### Getting Started - Grunt
28
28
29
29
To run patternlab-node using grunt, do the following in the directory you downloaded and extracted the zipped release:
30
30
31
31
1. Run `npm install` from the command line
32
-
2. Optionally, delete `package.gulp.json`, `gulpfile.js`, and `builder/patternlab_gulp.js` files if you are certain you don't need it.
33
-
* Not deleting `builder/patternlab_gulp.js` may cause a harmless error when running grunt. Delete it.
34
-
3. Run `grunt` or `grunt serve` from the command line
32
+
2. Optionally, delete `gulpfile.js`, `builder/gulp-core.js`, `builder/gulp-build.js` and `builder/gulp-extra.js` files if you are certain you don't need it.
33
+
3. Run `grunt` or `grunt pl:serve` from the command line
35
34
36
-
This creates all patterns, the styleguide, and the pattern lab site. It's strongly recommended to run `grunt serve` to have BrowserSync spin up and serve the files to you.
35
+
This creates all patterns, the styleguide, and the pattern lab site. It's strongly recommended to run `grunt pl:serve` to have BrowserSync spin up and serve the files to you.
37
36
38
37
### Getting Started - Gulp
39
38
40
39
To run patternlab-node using gulp, you need to swap out the default grunt configuration. Do the following in the directory you downloaded and extracted the zipped release:
41
40
42
-
1. Rename `package.json` to `package.grunt.json` or delete it if you don't intend on going back
43
-
2. Rename `package.gulp.json` to `package.json`
44
-
3. Run `npm install` from the command line
45
-
4. Run `gulp` or `gulp serve` from the command line
41
+
1. Run `npm install` from the command line
42
+
2. Optionally, delete `Gruntfile.js`, `builder/grunt-core.js` and `builder/grunt-build.js` files if you are certain you don't need it.
43
+
4. Run `gulp` or `gulp pl:serve` from the command line
46
44
47
-
This creates all patterns, the styleguide, and the pattern lab site. It's strongly recommended to run `gulp serve` to have BrowserSync spin up and serve the files to you.
45
+
This creates all patterns, the styleguide, and the pattern lab site. It's strongly recommended to run `gulp pl:serve` to have BrowserSync spin up and serve the files to you.
48
46
49
47
### There and Back Again, or Switching Between Grunt and Gulp
50
48
51
49
It's not expected to toggle between the two build systems, but for those migrating between the two configs, here's some general guidelines:
52
50
53
-
* Make sure your `package.json` files are correct per the Getting Started sections.
54
-
* Run `npm cache clear` before installation
55
-
* Delete the contents of `./node_modules` if you want a cleaner installation.
51
+
* Don't delete any files related to grunt or gulp. That's it!
52
+
* The `package.json` includes all dependencies for gulp **and** grunt so you can switch between the two without doing anything.
56
53
* Regarding speed, Gulp is faster. BrowserSync takes a bit longer than the old static server to spin up, but its capabilities far outweigh the startup cost.
57
54
58
55
### Upgrading
@@ -78,7 +75,7 @@ Get more information about patternlab-node, pattern lab in general, and where to
78
75
### Further Configuration
79
76
80
77
##### Watching Changes
81
-
To have patternlab-node watch for changes to either a mustache template, data, or stylesheets, run `grunt|gulp watch` or `grunt|gulp serve`. The `Gruntfile|Gulpfile` governs what is watched. It should be easy to add scss or whatever preprocessor you fancy.
78
+
To have patternlab-node watch for changes to either a mustache template, data, or stylesheets, run `grunt watch|gulp pl:connect` or `grunt|gulp pl:serve`. The `Gruntfile|Gulpfile` governs what is watched. It should be easy to add scss or whatever preprocessor you fancy.
82
79
83
80
##### Configurable Paths
84
81
Pattern Lab Node ships with a particular source and public workflow intended to separate the code you work on with the code generated for consumption elsewhere. If you wish to change any paths, you may do so within `config.json`. The contents are here:
banner: '/* \n * <%= pkg.name %> - v<%= pkg.version %> - <%= grunt.template.today("yyyy") %> \n * \n * <%= pkg.author %>, and the web community.\n * Licensed under the <%= pkg.license %> license. \n * \n * Many thanks to Brad Frost and Dave Olsen for inspiration, encouragement, and advice. \n *\n */\n\n',
0 commit comments