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

Use devDependencies #4

Open
herkyl opened this issue Jan 14, 2016 · 3 comments
Open

Use devDependencies #4

herkyl opened this issue Jan 14, 2016 · 3 comments

Comments

@herkyl
Copy link

herkyl commented Jan 14, 2016

Not really an issue but I wanted to see which modules feather uses by checking the package file but there is no way to know which modules are used for building and which are used in live code.

@HenrikJoreteg
Copy link
Owner

That's a good point, since only what's required gets pulled into the bundle at build time I didn't bother separating them out, but I didn't consider it from a viewer's perspective. I'll try to updated it when i have a minute, thanks!

@HenrikJoreteg
Copy link
Owner

The interesting thing about this is that arguably all the modules are dev dependencies because the resulting output is just static HTML, CSS and JS. There are no runtime dependencies.

Regardless, it probably makes sense to split between what's used directly in the client what isn't, which i suggested here: #6

@herkyl
Copy link
Author

herkyl commented Jan 19, 2016

@HenrikJoreteg it's pretty awesome that the app is frameworkless JS 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants