Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create starter repository with level/browserify/webpack examples #62

Closed
vweevers opened this issue Jan 18, 2019 · 6 comments
Closed

Create starter repository with level/browserify/webpack examples #62

vweevers opened this issue Jan 18, 2019 · 6 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@vweevers
Copy link
Member

Forked from Level/levelup#619, cc @fergiemcdowall.

We can use level-with-webpack-test as a starting point, maybe move the package to a subdirectory and add more subdirectories to demonstrate setups with browserify and others.

Or, create a starter repo for each? E.g. Level/level-with-webpack-starter.

@vweevers vweevers added documentation Improvements or additions to documentation good first issue Good for newcomers labels Jan 18, 2019
@fergiemcdowall
Copy link

Yes, maybe a single repo like level-with-webpack-test with a script command for every supported packaging tool: npm run build-with-browserify, npm run build-with-webpack, (and if we can get it to work) npm run build-with-rollup ?

BTW: things I like about level-with-webpack-test as it is now:

  • it is very terse, clear, and unpolluted by extraneous complications (test suites, linters, development servers, and other bells and whistles).
  • The source file is written in an ES6 style.

@vweevers
Copy link
Member Author

it is very terse, clear, and unpolluted by extraneous complications (test suites, linters, development servers, and other bells and whistles).

Yeah, that's why I'm leaning towards multiple starter repos (keeps dependencies and scripts clean). And level-with-webpack-test does have a linter atm (standard) but that was not intentional, we can remove it.

@vweevers

This comment has been minimized.

@vweevers
Copy link
Member Author

vweevers commented Jan 18, 2019

Poll time! How should we structure this?

image

Edit: poll has closed.

@vweevers
Copy link
Member Author

@vweevers
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants