We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Directly after yo dojo:
./build.sh -p ../../../profiles/myapp.profile.js --release processing profile resource /Users/dirk/work/myapp/profiles/myapp.profile.js discovering resources... starting reading resources... starting processing raw resource content... starting tokenizing resource... starting processing resource tokens... starting parsing resource... error(324) Error while transforming resource. resource: /Users/dirk/work/myapp/dojo/dojo.js; transform: 0; error: Error: ENOENT, open '/Users/dirk/work/myapp/dojo/dojo.js'
Using --dojoConfig:
./build.sh --dojoConfig ../../dojoConfig.js --release
dojo/dojox/dijit are minified in the release folder, but myapp is not.
Hopefully I'm just poking the bear the wrong way, but I can't seem to find a permutation of ./build.sh that works.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Directly after yo dojo:
./build.sh -p ../../../profiles/myapp.profile.js --release
processing profile resource /Users/dirk/work/myapp/profiles/myapp.profile.js
discovering resources...
starting reading resources...
starting processing raw resource content...
starting tokenizing resource...
starting processing resource tokens...
starting parsing resource...
error(324) Error while transforming resource. resource: /Users/dirk/work/myapp/dojo/dojo.js; transform: 0; error: Error: ENOENT, open '/Users/dirk/work/myapp/dojo/dojo.js'
Using --dojoConfig:
./build.sh --dojoConfig ../../dojoConfig.js --release
dojo/dojox/dijit are minified in the release folder, but myapp is not.
Hopefully I'm just poking the bear the wrong way, but I can't seem to find a permutation of ./build.sh that works.
The text was updated successfully, but these errors were encountered: