Is your feature request related to a problem? Please describe.
I am often having to manually check and update my npm dependencies. This would automate at least some of that process. https://greenkeeper.io

Description

The image generator tool creates placeholder images but that size is hard-coded. I need to add a flag to set the horizontal and vertical size.

Description

The current Open Sans font stack was not optimized for the web. svg and woff2 can be dropeed from the font stack as well.

Is your feature request related to a problem? Please describe.
There is a lot of unused css which could be removed in production builds.

Describe the solution you'd like
The likely solution will be to use uncss in a custom node script. This would run after webpack-build production. It would remove the styles.gz file, analyze the styles.css file, remove the css and then create a new gzip stylesheet.

Describe alternatives you've considered

• https://github.com/FullHuman/purgecss-webpack-plugin - Unable to remove classes added by bootstrap JS ('.show', '.fade', etc.); could create a whitelist of these classes but it would be a large list that could easily become outdated
• https://github.com/webpack-contrib/purifycss-webpack - Now deprecated

Additional context
N/A

The webpack configuration currently is tailored to creating a single page. Allowing users to set up multiple pages right away, or at the very least, provide documentation on how to add multiple pages, would be useful.

Description

The image placeholder file is mearly there to demonstrate creating images in the source and copying them to the dist. The placeholder file here should be as small as possible.

The ability to output an image 1 at a time is a bit limiting, sometimes it would be nice to define a set (array?) or image sizes to be output all at once. This might work best as a separate file (JSON? comma delimited list?).

Example

{
    "images": [
        {
            "title": "banner",
            "width": 1200, 
            "height": 320, 
            "quality": 100
        },
        {
            "title": "thumbnail",
            "width": 80, 
            "height": 80, 
            "quality": 100
        }
    ]
}

Describe the bug
js-image-generator should be in devDependencies not dependencies

openlayers-workshop-en had a nice webpack setup for getting running quickly

Description

The distribution needs to be gzipped

Is your feature request related to a problem? Please describe.
Right now only a single entry point is used. This means that only 1 compressed CSS file is used on every page.

Describe the solution you'd like
There should be a clear and easy approach to setting up multiple CSS files for different pages.

Describe alternatives you've considered
Might need to look for an alternative to mini-css-extract-plugin

Is your feature request related to a problem? Please describe.

• Add a _custom.scss to override bootstrap using SASS.

The devDependency webpack was updated from 4.35.3 to 4.36.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Describe the solution you'd like
A few options worth exploring:

• gh-pages to make deploying to github.io a breeze. I have used this in other repositories.
• ftp-deploy - This might make the most sense. Since bootpack is desigend for web designer/developers who are use to working with FTP servers.
• Custom ssh deploy script

Description

Create an npm script that can build bootstrap example templates

Would build these examples with only the required imports needed. (Plus have a flag to include full BS4 code).
https://getbootstrap.com/docs/4.0/examples/

Thinking something long the lines of:
npm run build generate:bs4 -- generates bare bs4 template with mimum imports
npm run generate:bs4-album --full -- generates bs4 album template with full bs4 import included

Description

I noticed that bootstrap was overriding my declarations when targeting the same selector. Further investigation reveled bootstrap was coming after my custom css even though the @imports were in the correct order within main.css.

Describe the bug
Currently webpack is not properly watching changes to the html files.

Expected behavior

• npm run watch should use webpack-dev-server.
• Template paths should be added to index.js and detect changes if NODE_ENV=development
• A npm run build:dev option should be added to debug non-server output

Is your feature request related to a problem? Please describe.
Bootstrap has a number of free 'navbars' templates which can be added to the bootpack template directory.

Describe the solution you'd like
Add the current templates from here: https://getbootstrap.com/docs/4.3/examples/#navbars

Is your feature request related to a problem? Please describe.
Bootstrap has a number of free 'experiments' templates which can be added to the bootpack template directory

Describe the solution you'd like
Add the current templates from here: https://getbootstrap.com/docs/4.3/examples/#experiments

• Issue Template
• Pull Request Template
• Code of Conduct Doc
• Contributing Doc

Is your feature request related to a problem? Please describe.
Minified css files need to be cache busted by outputting the min files with a hash.

Describe the solution you'd like
Add a hash to the dist/main.css file

Describe alternatives you've considered
None

Additional context
None

Is your feature request related to a problem? Please describe.
It would be nice to have an elements template(s) with all bootstrap content, components and utilities organized in one area.

Describe the solution you'd like
Add an element template(s) with content, components & utilities:

• https://getbootstrap.com/docs/4.3/content/typography/
• https://getbootstrap.com/docs/4.3/components/alerts/
• https://getbootstrap.com/docs/4.3/utilities/borders/

Is your feature request related to a problem? Please describe.
Output the version number in the console (terminal & browser console) to easily find the version being ran.

Describe the solution you'd like

• Output version to terminal on build
• Output version in browser console

Add CI/CD. Most likely this will be Travis CI but worth exploring other options

Add documentation on how to use the image generator tool from the command line

Describe the bug
The favicon relative path within the subpages is not updated when injected into the html.

Additional context
Since the original favicon package I used was no longer being actively supported, I created another favicon package here: https://github.com/bootpack/favicons-plugin to update old dependencies and fix this issue.

Using a newer version of loader-utils and performing better checks against the publicPath should resolve this issue. That work will be referenced here: bootpack/favicons-plugin#1

Note: We are also not setting the publicPath in our webpack config for various reasons. This may change in the future. Setting publicPath currently to / would allow this package to work properly with webpack-dev-server but would break when opening dist files locally. Addiionally, the css paths on subpages breaks when setting the publicPath to / but rel paths are injected properly when this field is omitted.

Is your feature request related to a problem? Please describe.
Automatically deploy the dist directory to bootpack.github.io. This will allow users to see what the template will look like when built.

Describe the solution you'd like
Remove the separate bootpack.github.io repository and utilize git worktree add dist gh-pages to push the contents of the dist directory to the gh-pages branch

Tasks

• Add documentation in the README.md to point users to the latest production build (https://bootpack.github.io/bootpack)

Describe the bug
When running npm start, npm run build or npm run watch, favicon generation only occurs if the dist directory does not already contain favicons. If the dist directory does contain favicons from a previous build, the next build will not have any icons output.

To Reproduce
Steps to reproduce the behavior:

1. Run npm start
2. Observe favicons in dist directory
3. Run npm start
4. Observe no favicons in dist directory

Expected behavior
Favicons generate on every build.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Description

Currently there are no favicons in the application. There should be default favicons for all the PWA platforms (Android, iOS, Windows, etc.)

Is your feature request related to a problem? Please describe.
Bootstrap is not being imported into index,js and main.css does not include all bootstrap sass files.

Describe the solution you'd like
main.css and index.js should have the full bootstrap bundles imported by default but also individual components commented out below so that advanced users can import only what is needed.

jQuery global $ should also be exposed via the webpack config file

Describe alternatives you've considered
None

Additional context
None

Is your feature request related to a problem? Please describe.
Bootstrap has a number of free 'custom component' templates which can be added to the bootpack template directory.

Describe the solution you'd like
Add the current templates from here: https://getbootstrap.com/docs/4.3/examples/#custom-components

Is your feature request related to a problem? Please describe.
It would be nice to have a method for auto optimizing images in the src folder and piping these to the dist folder

Describe the solution you'd like
compress-images images is a good npm package that can handle this. I have used this dependency in the past to create custom image optimization pipelines. It can optimize gif, png, svg, and jpeg via a multitude of engines one can choose.

Describe the bug
Currently bootstrap components are not handled correctly. The boostrap/js/src is imported so dependency imports work but it is not being babelified. Imports should be switched to point to the bootstrap/js/dist then, include jQuery slim, popper, and bootstrap util in webpack.

Describe the bug
4 Travis CI checks are occuring when there should only be 1 for the branch and 1 for creating a pull request.

Expected behavior
Only use "Branch" and "Pull Request" checks.

Screenshots

Description

Incorporate a node.js favicon generator.

Performing npm generator:favicon would build all the progress web app favicons and extract them to a "favicons" src folder. When the source is ran through webpack, all the favicons would be placed and gzipped into the root of the dist folder. There should be options to turn on/off different sizes.

Here is the first library I found for a node.js favicon generator: https://github.com/evilebottnawi/favicons Other dependency libraries should be researched (or decide if this needs written from scratch).

Is your feature request related to a problem? Please describe.
Investigate the possibility of adding a icon font generator.

Describe the solution you'd like
icomoon cli tool

Describe alternatives you've considered
Font Awesome 5