Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Define main as the entry-point files, one-per-filetype #43
Maybe we should also note that each entrypoint specifies both main file and loadpath.
It's similar to how require.js defines work. That's how I think about it at least.
When I say load path I mean something like
It means that:
This "load path" also exists in other module systems. For example
Load path is core idea of many module systems, and bower probably should account for that.
I already said it in other channels, but I'm not a big fan of "one entry-point per filetype". From all proposals I think this is the one which offers the least features and while it is often good to not have a lot of features for complexity reasons I think they are necessary here so Bower is beneficial enough to coexist and be maintained next to npm, because it is more specific to front end code and assets, instead of adding some front end specific logic to npm and package.json itself and drop Bower.
What do we get here?
What do we don't get?
@donaldpipowitch Thank you for this input. You raise several good issues. The larger issue that we're addressing here is how