In a regular YUI App, the seed file is just the YUI Seed file, and by including it in your pages in a form of a script tag you are ready to use YUI, e.g.:
<script src="http://yui.yahooapis.com/3.7.3/build/yui/yui-min.js"></script>
From that url, the library can infer few things like the version of the library that should be used, the filter that you want to use (min, debug or raw), the CDN that is serving the library, etc. But when it comes to a mojito application, things are a little bit different, since the YUI library is bundle with the application using npm
, and the way your application runs might also disrupt from a regular web application when it comes to mobile. On top of that, the introduction of a lot of new YUI modules, part of the mojito code, and part of the app code that should work in the same way that YUI Core modules work through the loader, all that makes it difficult to use the standard way for the seed in a mojito application.