Quantcast
Channel: JavaScriptMVC Forum
Viewing all articles
Browse latest Browse all 3491

Steal production build

$
0
0
Hello,

We have been using JavascriptMVC in a project for more than a year now, and have created and used the production builds successfully.

Earlier this month, we updated to the latest versions of can/steal/funcunit/jquerypp/canui/documentsjs, as indicated by this link : https://github.com/bitovi/javascriptmvc

After making all the necessary changes/updates to our code, the application works fine in the development mode.

While creating the production build, I have run into an issue where certain files dont seem to have been minimized/packaged, and when the application runs in the production mode, it steals the original uncompressed file.

I found a possible reason for this:

This is my folder structure:

testing (folder)
--- sample.js
--- metadata (folder)
metadata.js

sample.js :

  1. steal("jquery","jquery/controller","./metadata",function(){
  2. $.Controller.extend("Sample",{},{
  3. init : function(){
  4. this.sample = "sample";
  5. }
  6. });
  7. }
  8. );
build.js :
  1. steal.packages("testing/sample.js")
When building the above, metadata/metadata.js does not get included in the production build (in the compressed file)

If I change the line marked in red in sample.js to the following :

  1. "./metadata/metadata.js"

I am now able to see the contents of metadata.js in the compressed file.

Is this a rule/convention to be followed with the new version, that entire js paths should be specified ?

The same code used to work earlier before the upgrade.


Viewing all articles
Browse latest Browse all 3491

Trending Articles