stealjs / grunt-steal

Use StealJS to build your projects with Grunt.

StealJS

StealJS is an awesome front-end module loader that makes writing large applications easy. Learn more at stealjs.com.

This repository houses the source for the website.

Contributing

If you’d like to have your Steal plugin added under the Ecosystems section on the website, please add an issue and we can discuss it.

If you want to work on the website, first clone it:

git clone https://github.com/stealjs/stealjs.git

Then install the dependencies:

npm install

Then generate the documentation:

npm run document

License

Steal, StealTools, and all sub-projects are licensed under the MIT License.

grunt-steal's Issues

An in-range update of steal-tools is breaking the build 🚨

Version 1.3.4 of steal-tools just got published.

Branch	Build failing 🚨
Dependency	steal-tools
Current Version	1.3.3
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

steal-tools is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 30 commits.

• 0b7a0b9 1.3.4
• d1ddfed Merge pull request #709 from stealjs/ignore-uglify
• 0dad54e Merge pull request #713 from stealjs/export-stuff
• 96f1248 Adds buildResult as resolved value for stealTools.export
• a556a9a Set greenkeeper to ignore uglify-js
• 9e6a405 Merge pull request #704 from stealjs/pump
• a94d072 Merge pull request #705 from stealjs/bundle-docs
• dc1d31f Fix steal-tools bundle docs
• d39524d Simplify steal-tools bundle with pump library
• fea3bd9 Merge pull request #703 from stealjs/pump
• b0697e0 Use pump library in steal-tools build code
• d461624 Merge pull request #685 from stealjs/conditional-with-extensions
• 7edd2c3 Use [email protected]
• b7e1702 Merge pull request #694 from stealjs/greenkeeper/yargs-8.0.1
• 060d751 Merge pull request #697 from stealjs/pYr0x-patch-1

There are 30 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Fatal error: Arguments to path.join must be strings

I'm currently getting the following error when I try a grunt-steal build.

Building ./build/releases/production.js
steal.compress - Using Uglify
steal.compress - Using Uglify
Fatal error: Arguments to path.join must be strings
TypeError: Arguments to path.join must be strings
at path.js:360:15
at Array.filter (native)
at Object.exports.join (path.js:358:36)
at tryPathIndex (/Users/ecarino/p4depot/EricsMacBookAir_ManhattanClient/web/node_modules/grunt-steal-node/node_modules/steal-tools/node_modules/less/lib/less/index.js:195:37)
at callback.type (/Users/ecarino/p4depot/EricsMacBookAir_ManhattanClient/web/node_modules/grunt-steal-node/node_modules/steal-tools/node_modules/less/lib/less/index.js:198:29)
at Object.oncomplete (fs.js:107:15)

Version Info:

grunt 0.4.5
grunt-cli 0.1.13
node 0.10.26
grunt-steal-node 0.2.5

Gruntfile.js entry:

steal: {
    dist: {
        src: 'exo/exo.js',
        dest: './build/releases'
    }
},

Document grunt-steal under Ecosystem

Individual build files

Issue by alexisabril from Thursday Jan 17, 2013 at 19:00 GMT
Originally opened as https://github.com/alexisabril/grunt-steal/issues/5

---

Add ability to build individual projects(if multiple are specificed)

Update options to be 1.0 compatible

Such as changing the export task to use steal in place of system.

Exit status code

Issue by alexisabril from Thursday Oct 18, 2012 at 16:14 GMT
Originally opened as https://github.com/alexisabril/grunt-steal/issues/3

---

Currently we're returning the stdout regardless of error, but we should trigger a grunt error if exec does not complete successfully.

Grunt Targets not working

Issue by falzhobel from Friday Dec 06, 2013 at 21:40 GMT
Originally opened as https://github.com/alexisabril/grunt-steal/issues/10

---

Tried the following to make specific grunt-steal targets :

steal: {
  front: {
    js: 'jmvc',
    build: [{
      src: 'app/global/scripts/build.js',
      to: 'app/global',
      compressor: 'uglify'
    }]
  },
  cms: {
    ...
  }
},

...

grunt.loadNpmTasks('grunt-steal');
grunt.registerTask('buildjsfront', 'steal:front');

Here's what I get with the --verbose --stack --debug flags when running grunt buildjsfront:

Running "buildjsfront" task
[D] Task source: trunk/gruntfile.js

Running "steal:front" (steal) task
[D] Task source: trunk/node_modules/grunt-steal/tasks/steal.js
Verifying property steal exists in config...OK
Warning: Cannot read property 'src' of undefined Use --force to continue.
TypeError: Cannot read property 'src' of undefined
    at execute (trunk/node_modules/grunt-steal/tasks/steal.js:43:21)
    at Object.<anonymous> (trunk/node_modules/grunt-steal/tasks/steal.js:75:5)
    at Object.thisTask.fn (trunk/node_modules/grunt/lib/grunt/task.js:78:16)
    at Object.<anonymous> (trunk/node_modules/grunt/lib/util/task.js:282:30)
    at Task.runTaskFn (trunk/node_modules/grunt/lib/util/task.js:235:24)
    at Task.<anonymous> (trunk/node_modules/grunt/lib/util/task.js:281:12)
    at Task.<anonymous> (trunk/node_modules/grunt/lib/util/task.js:215:7)
    at Task.runTaskFn (trunk/node_modules/grunt/lib/util/task.js:238:9)
    at Task.<anonymous> (trunk/node_modules/grunt/lib/util/task.js:281:12)
    at Task.start (trunk/node_modules/grunt/lib/util/task.js:290:5)

Thanks for the plugin, been using it for a couple months now.

Grunt 0.4 Release

Issue by tkellen from Friday Feb 15, 2013 at 20:17 GMT
Originally opened as https://github.com/alexisabril/grunt-steal/issues/8

---

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴