Describe the bug
Builds fail when output dir is not defined

To Reproduce
Steps to reproduce the behavior:

1. svb -i src/index.js -o some/unkown/dir

Expected behavior
Should generate all directories listed, using mkdirp.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: [e.g. macOS 10.14.5]
• svb Version: [eg: 0.1.0]
• NodeJS Version: [eg: v12.5.0]

Additional context or comments
Maybe we should delete the output dir before a build? Does mkdirp do that?

Is your feature request related to a problem? Please describe.
Problem: currently only CSS and JS bundles are produced. We should create (or use a userland template) for an index.html file that could actually be loaded.

Describe the solution you'd like
An index.html file is generated/converted from a template and pulls in the JS and CSS bundles.

Additional context
Not sure where the userland template should live, also if we should fall back to something else if it's not there.

Is your feature request related to a problem? Please describe.
Users may wish to customize the name of the outputted bundle.css and bundle.js files.

Describe the solution you'd like
Perhaps an option or flag for customizing the names?

Additional context
Side note: What about being able to optionally include a hash on the filename, to help with cache busting?

Is your feature request related to a problem? Please describe.
Users are going to need something to deal with images/video/media/etc.

Describe the solution you'd like
There should be something in the build step to handle assets I guess.

Describe alternatives you've considered
Like in some ways this almost goes against the concept of this being a "small" bundler, but in general like folks should be able to handle assets like this.

Additional context

• https://github.com/rollup/rollup-plugin-image

Is your feature request related to a problem? Please describe.
Users could pass in an option to specify where the HTML file is located.

Describe the solution you'd like
--template or something like that

Describe alternatives you've considered
Similar to #2, but slightly more distinct.

Describe what needs to be done

• To help folks understand how to use this package (and also to help test things), let's include an example/ project.

Are there any dependency updates?

• N'est pas

Is your feature request related to a problem? Please describe.
Users might want to have source maps generated.

Describe the solution you'd like
Generate JS (and CSS?) source maps for
Should be an opt-out kind of option (so generate them by default).

Describe alternatives you've considered
N'est pas!

Additional context

• https://www.npmjs.com/package/rollup-plugin-sourcemaps
• https://github.com/Rich-Harris/sorcery

Describe what needs to be done

• Add coveralls for test coverage data.

Are there any dependency updates?

• yep, coveralls

Is your feature request related to a problem? Please describe.
Set sensible defaults and explore the best practices for CSS generation.

Describe the solution you'd like

• rollup-plugin-postcss
• Autoprefixer?
• IDK, explore

Additional context
Not sure what needs to be done here specificall.

Describe what needs to be done

• Setup travis.ci once all the testing stuff gets set up

Is your feature request related to a problem? Please describe.
Users will probably want to run this in "watch" mode to allow for rapid development.

Describe the solution you'd like
It should use rollup's watch mode, along with anything else which might make the dev experience even better (such as nicer error reporting if the compile step fails -- just like create-react-app).

What a difference between this package and sveltejs/template except the moment that this packages makes not possible to customize you bundle configuration?

Describe the bug
[Bug] Index/template file is not generated on first --watch run, when run on a fresh directory.

To Reproduce
Steps to reproduce the behavior:

1. svb -i src/index.js -o empty/directory/ -w

Expected behavior
Should build & bundle the template on every run. Just saying. Even in watch mode.

Versions (please complete the following information):

• svb Version: 0.3.0.beta.0
• NodeJS Version: v12.8.1

Additional context or comments
Add any other context about the problem here.

Describe what needs to be done

• Add tests to ensure it actually works from a user perspective (ie: running the command actually produces the files in the places which it should).

Are there any dependency updates?

• None, unless any are needed to assist with this.

Describe what needs to be done

• Use docsify for proper documentation on how to use this boiii.

Are there any dependency updates?

• Yep, docsify globallly

Describe what needs to be done

• Add some unit testing for modules/code which should be unit tested.

Are there any dependency updates?

• Nope Add Jest

Describe what needs to be done

• Add ESLinting
• Can just use this bad boi (for now).

Are there any dependency updates?

• Yeap gonna be adding some deps.

Is your feature request related to a problem? Please describe.
Users might want to eject and in theory we should support that. That way this project can remain opinionated while allowing for users to do their own thing if they choose.

Describe the solution you'd like

• svb --eject or something.
• An "are you sure" prompt.

Describe alternatives you've considered
Not sure if this should be done or not, but it's not critical for getting this project off the ground.