Skip to content

Commit

Permalink
Added .npmignore file
Browse files Browse the repository at this point in the history
Without it, .gitignore was used by npm for publishing, which excluded
the `build` directory.
  • Loading branch information
anowak committed May 21, 2015
1 parent 747cce2 commit c7cc522
Show file tree
Hide file tree
Showing 6 changed files with 10 additions and 4 deletions.
1 change: 0 additions & 1 deletion .gitignore
@@ -1,4 +1,3 @@
node_modules/
build/
src/templates/*.js
.*.swp
2 changes: 2 additions & 0 deletions .npmignore
@@ -0,0 +1,2 @@
node_modules/
.*.swp
4 changes: 3 additions & 1 deletion CHANGELOG.md
@@ -1,6 +1,8 @@
## 0.2.1 (May 21, 2015)
## 0.2.2 (May 21, 2015)

* Corrected publishing as Node.js module (`package.json` now contains correct main entry point)
* Corrected `.npmignore`, so the build artifacts are actually published to npm. Unpublished version
0.2.1 that was built with incorrect `.npmignore` file.

## 0.2.0 (Apr 23, 2015)

Expand Down
3 changes: 3 additions & 0 deletions README.md
Expand Up @@ -29,6 +29,9 @@ to a Flash-based approach (such as [Downloadify](https://github.com/dcneiner/Dow
Our demo does not include this workaround to keep things simple, so it will not work on Safari at
this point of time.

You can also find a sample for using it in Node.js environment
[here](https://github.com/evidenceprime/html-docx-js-node-sample).

To generate DOCX, simply pass a HTML document to `asBlob` method to receive `Blob` (or `Buffer`)
containing the output file.

Expand Down
2 changes: 1 addition & 1 deletion bower.json
@@ -1,6 +1,6 @@
{
"name": "html-docx-js",
"version": "0.2.1",
"version": "0.2.2",
"description": "Converts HTML documents to DOCX in the browser",
"repository": {
"type": "git",
Expand Down
2 changes: 1 addition & 1 deletion package.json
@@ -1,6 +1,6 @@
{
"name": "html-docx-js",
"version": "0.2.1",
"version": "0.2.2",
"description": "Converts HTML documents to DOCX in the browser",
"main": "build/api.js",
"repository": {
Expand Down

0 comments on commit c7cc522

Please sign in to comment.