Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / cujojs/cram issues and pull requests

#48 - Read --exclude options from files

Issue - State: closed - Opened by fedevegili over 9 years ago - 1 comment

#47 - Cram not working

Issue - State: closed - Opened by tungd about 10 years ago - 2 comments

#46 - Cram 0.8.2 does not set exit code to non-zero when it failes

Issue - State: open - Opened by OOPMan about 10 years ago

#45 - cram is missing two require() calls in rest/mime/registry

Issue - State: closed - Opened by unscriptable over 10 years ago - 1 comment

#44 - fix runAsModule detection with regexp

Pull Request - State: closed - Opened by gogamoga over 10 years ago - 3 comments

#43 - Hopefully this does not break anything else

Pull Request - State: closed - Opened by gogamoga over 10 years ago - 1 comment

#42 - did you publish new version without amd_modules?

Issue - State: closed - Opened by gogamoga over 10 years ago - 11 comments

#41 - Check that promise is not fulfilled too early

Issue - State: closed - Opened by bclozel over 10 years ago - 4 comments

#40 - Empty multi-line array of dependecies causes error.

Issue - State: closed - Opened by fedevegili over 10 years ago - 1 comment

#39 - Does not do anything if run from an npm script

Issue - State: closed - Opened by unscriptable over 10 years ago - 1 comment

#38 - cram thinks the `require()`s in rest/mime/registry are global

Issue - State: closed - Opened by unscriptable over 10 years ago - 3 comments

#37 - cram fails on the seed project

Issue - State: closed - Opened by stanislawosinski over 10 years ago - 6 comments

#36 - cram/test/examples all fail with cram 0.7.8

Issue - State: closed - Opened by deciob almost 11 years ago - 1 comment

#35 - Give grokked default properties as bandage for not giving Cram a curl config

Pull Request - State: closed - Opened by phated almost 11 years ago - 1 comment

#34 - EMFILE error

Issue - State: open - Opened by gehan almost 11 years ago - 3 comments

#33 - amd_modules folder missing after installing cram from npm

Issue - State: closed - Opened by jsedlacek almost 11 years ago - 4 comments

#32 - Postinstall of Bower dependencies breaks with sudo

Issue - State: closed - Opened by phated almost 11 years ago - 9 comments

#31 - i18n plugin problem

Issue - State: open - Opened by gehan about 11 years ago

#29 - Don't detect goog.require('id') as a sync require

Issue - State: closed - Opened by unscriptable about 11 years ago - 1 comment

#28 - Issue getting started with cram. "Protocol not supported"

Issue - State: closed - Opened by johanchouquet about 11 years ago - 18 comments

#27 - Process includes in config as well as in args

Pull Request - State: closed - Opened by gehan about 11 years ago

#26 - Detect moduleLoaders properly and don't prepend name to module like with a plugin

Pull Request - State: closed - Opened by gehan about 11 years ago - 2 comments

#25 - cram should not output the moduleLoader's prefix to the bundle

Issue - State: closed - Opened by unscriptable about 11 years ago - 2 comments

#24 - cram gets confused with lodash.js

Issue - State: closed - Opened by unscriptable about 11 years ago - 21 comments

#23 - Working excludes example

Pull Request - State: closed - Opened by gehan about 11 years ago - 2 comments

#22 - No way to override loader if it is grokked

Issue - State: open - Opened by unscriptable about 11 years ago

#21 - Cram on windows

Issue - State: closed - Opened by neoroma about 11 years ago - 2 comments

#19 - Create a programmatic API

Issue - State: closed - Opened by unscriptable over 11 years ago - 5 comments

#17 - Create docs for creating build-time plugins

Issue - State: open - Opened by unscriptable over 11 years ago - 5 comments

#16 - Add bin file for npm usage

Pull Request - State: closed - Opened by gehan over 11 years ago - 6 comments

#15 - has no method 'config'

Issue - State: closed - Opened by ghost over 11 years ago - 1 comment

#14 - add defineName and defineContext config options

Issue - State: closed - Opened by unscriptable over 11 years ago - 1 comment

#11 - cram.js hangs when using 'dojo/io/script'

Issue - State: closed - Opened by unscriptable over 11 years ago - 1 comment

#10 - cram.js is too greedy when finding factory function in define()

Issue - State: closed - Opened by unscriptable over 11 years ago - 1 comment

#9 - CSS filename gets prepended to url() string

Issue - State: closed - Opened by zourtney over 11 years ago - 6 comments

#8 - Multiline dependency array parsing issue

Issue - State: closed - Opened by zourtney over 11 years ago - 2 comments

#7 - Error in compiled javascript

Issue - State: closed - Opened by joefiorini over 11 years ago - 5 comments

#6 - Fixes running cram with a supplied config file

Pull Request - State: closed - Opened by joefiorini almost 12 years ago - 1 comment

#5 - Using wire with cram

Issue - State: closed - Opened by joefiorini almost 12 years ago - 8 comments

#4 - rewrite to use curl.js internally

Issue - State: closed - Opened by unscriptable almost 12 years ago - 3 comments

#3 - Unclear how to use wire/cram/builder.js

Issue - State: closed - Opened by dizzib over 12 years ago - 7 comments

#2 - optimizer should use apiContext, apiName, defineContext, and defineName

Issue - State: open - Opened by unscriptable over 12 years ago - 1 comment

#1 - Status?

Issue - State: closed - Opened by asilvas about 13 years ago - 9 comments