alternative package.js problem

edited March 2012 in Enyo 2
Just noticed while working on updating the tutorial to include Onyx that if you try to have an alternative version of your package.js in the folder, the dependency loader, aka enyo.depends() may misbehave. I'd cloned the search.html file into search-onyx.html which pulled in package-onyx.html. That pulled in other libraries, but then failed to pull in the local source files because it got mixed up about where to search. Moving the second version into its own folder and renaming package-onyx.json back to package.json let everything work again as expected.

I'm checking with Scott to see if this is expected behavior or a bug, but wanted to post it here in case anyone had seen similar things.
Sign In or Register to comment.