From 36b724e182ddbf6c6b56c001dbb1b9b5b186fe3b Mon Sep 17 00:00:00 2001 From: Albert Groothedde Date: Mon, 22 Jun 2015 13:55:47 +0200 Subject: [PATCH 1/4] Main should be a place for libraries, not sources The main should contain files that can be used as library, not as sources. They can also contain the sources in forms of `less`, `sass`, or even `d.ts` files, so that the consuming party can choose based on filetype what to use and include in the project. Arguably even `.min.js` can also be added as it's the 'definitive' version of a 'compiled' library. See also twbs/bootstrap compliance to the spec issues: https://github.com/twbs/bootstrap/issues/16663 --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 58f9ec7..38814c8 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ The package's semantic version number. *Recommended* Type: `String` or `Array` of `String` -The entry-point files necessary to use your package. Only one file per filetype. +The entry-point files necessary to use your package. Only one file per filetype. The files that are offered should be representing your package as library. This means that the files can be used without compiling for use by the consuming party. Entry-point files have module exports and may use module imports. While Bower does not directly use `main` files, they are listed with the commands `bower list --json` and `bower list --paths`, so they can be used by build tools. @@ -81,6 +81,10 @@ Let's say your package looks like this: "main": [ "js/motion.js", "sass/motion.scss", + "img/motion.png", + "fonts/icons.woff", + "fonts/icons.woff2", + "dist/movement.css" ] ``` From 926f3b9c50262dd68eccf9d1b803abc31c610a5b Mon Sep 17 00:00:00 2001 From: Albert Groothedde Date: Mon, 22 Jun 2015 14:11:02 +0200 Subject: [PATCH 2/4] Removed image and font files --- README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/README.md b/README.md index 38814c8..55cf56b 100644 --- a/README.md +++ b/README.md @@ -81,9 +81,6 @@ Let's say your package looks like this: "main": [ "js/motion.js", "sass/motion.scss", - "img/motion.png", - "fonts/icons.woff", - "fonts/icons.woff2", "dist/movement.css" ] ``` From a93cd95e639d6bb421ba4ac5f75e791256e650bb Mon Sep 17 00:00:00 2001 From: Albert Groothedde Date: Tue, 23 Jun 2015 15:55:19 +0200 Subject: [PATCH 3/4] Compiled and css, less, sass Added that the 'main' is not **only** for the compiled version, but also for the versions that can be used as libraries in case of `less`, `sass`, and maybe even `ts` files. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 55cf56b..149f90f 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ The package's semantic version number. *Recommended* Type: `String` or `Array` of `String` -The entry-point files necessary to use your package. Only one file per filetype. The files that are offered should be representing your package as library. This means that the files can be used without compiling for use by the consuming party. +The entry-point files necessary to use your package. Only one file per filetype. The files that are offered should be representing your package as library. This means that the files can be used without compiling for use by the consuming party. This is not limited to **only** the 'compiled' version. In case of `.less`, `.scss` or `(d).ts` etc. they can be used as library aswell when used in the consuming party source. Entry-point files have module exports and may use module imports. While Bower does not directly use `main` files, they are listed with the commands `bower list --json` and `bower list --paths`, so they can be used by build tools. From e09462922479dd288c03e4f4e7c4fa6687e0662c Mon Sep 17 00:00:00 2001 From: Albert Groothedde Date: Wed, 24 Jun 2015 17:00:36 +0200 Subject: [PATCH 4/4] Typo aswell > as well --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 149f90f..01709f0 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ The package's semantic version number. *Recommended* Type: `String` or `Array` of `String` -The entry-point files necessary to use your package. Only one file per filetype. The files that are offered should be representing your package as library. This means that the files can be used without compiling for use by the consuming party. This is not limited to **only** the 'compiled' version. In case of `.less`, `.scss` or `(d).ts` etc. they can be used as library aswell when used in the consuming party source. +The entry-point files necessary to use your package. Only one file per filetype. The files that are offered should be representing your package as library. This means that the files can be used without compiling for use by the consuming party. This is not limited to **only** the 'compiled' version. In case of `.less`, `.scss` or `(d).ts` etc. they can be used as library as well when used in the consuming party source. Entry-point files have module exports and may use module imports. While Bower does not directly use `main` files, they are listed with the commands `bower list --json` and `bower list --paths`, so they can be used by build tools.