Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / RaveJS/rave issues and pull requests
#78 - CoffeeScript support
Issue -
State: open - Opened by punund over 8 years ago
#77 - Where is require()
Issue -
State: open - Opened by CNSKnight about 9 years ago
- 3 comments
#76 - Error: AMD define not called
Issue -
State: open - Opened by CNSKnight about 9 years ago
- 3 comments
#75 - Why not contribute to System.js?
Issue -
State: closed - Opened by edrex about 9 years ago
- 1 comment
#74 - Rave devlopment
Issue -
State: closed - Opened by szepeviktor about 9 years ago
- 2 comments
#73 - Loading remote scripts
Issue -
State: closed - Opened by szepeviktor about 9 years ago
- 2 comments
#72 - Please tell me, Who to build production version?
Issue -
State: open - Opened by icode over 9 years ago
- 3 comments
#71 - Cross-origin error reporting
Issue -
State: open - Opened by szepeviktor over 9 years ago
- 2 comments
#70 - Even if there is not the JSON, the rave.missing does work.
Pull Request -
State: open - Opened by atomita over 9 years ago
- 2 comments
#69 - Base url option?
Issue -
State: closed - Opened by Bitaru over 9 years ago
- 4 comments
#68 - Unnecessary 404 for the package.json of a peerDependency
Issue -
State: open - Opened by teehemkay over 9 years ago
#67 - Rave can't handle relative paths
Issue -
State: open - Opened by gregturn over 9 years ago
#66 - Problem loading JSON file.
Issue -
State: closed - Opened by teehemkay over 9 years ago
- 5 comments
#65 - fixed filename for case-sensitive file systems
Pull Request -
State: closed - Opened by rhmoller over 9 years ago
- 2 comments
#64 - Support npm's forthcoming Ecosystems and Collections
Issue -
State: open - Opened by unscriptable almost 10 years ago
- 2 comments
#63 - Breakpoints in Firebug are ineffective
Issue -
State: open - Opened by unscriptable almost 10 years ago
#62 - Rave should default to "debug mode" except for production.
Pull Request -
State: closed - Opened by unscriptable almost 10 years ago
- 1 comment
#61 - Very simple build attempt
Pull Request -
State: closed - Opened by unscriptable almost 10 years ago
- 1 comment
#60 - why has directories.lib support been added
Issue -
State: open - Opened by KidkArolis almost 10 years ago
- 5 comments
#59 - Consider dropping support for bower
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 8 comments
#58 - Stop defaulting the moduleType metadata property. Auto-detect instead.
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 3 comments
#57 - When bower.json is missing, the default moduleType is ["node"]
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 2 comments
#56 - Rave gives cryptic errors for missing modules ("fs" and "traceur") when app's moduleType is missing
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 3 comments
#55 - The rave.missing feature does not work for the metadata "dependencies" property
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 2 comments
#54 - Cryptic error message when a package's metadata is missing "main"
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 1 comment
#53 - jQuery doesn't register as AMD
Issue -
State: closed - Opened by unscriptable almost 10 years ago
- 1 comment
#52 - Fails to load browserified bundle from node_modules
Issue -
State: open - Opened by briancavalier almost 10 years ago
- 1 comment
#51 - Rave as a generic loader
Issue -
State: open - Opened by KidkArolis almost 10 years ago
- 3 comments
#50 - "rave.missing" and "rave.overrides" properties should override package.json and bower.json metadata, not override rave's internal representation of the metadata
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 1 comment
#49 - Apply rave.missing as default overrides from all rave extensions. See #43.
Pull Request -
State: closed - Opened by unscriptable about 10 years ago
- 9 comments
#48 - Rave fails to load bower components installed in a directory other than the default "bower_components" directory.
Issue -
State: open - Opened by teehemkay about 10 years ago
- 7 comments
#47 - Review the README.MD to fully show the benefits and power of RaveJS
Issue -
State: open - Opened by fabricematrat about 10 years ago
- 1 comment
#46 - Auto-sniff for AMD when moduleType is unknown.
Pull Request -
State: closed - Opened by unscriptable about 10 years ago
- 7 comments
#45 - Auto-sniff module type when moduleType is missing from bower packages
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
#44 - Allow devs to opt-in to overrides from third-party rave extensions.
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 6 comments
Labels: enhancement
#43 - Create rave-common-overrides repo to fix broken packages
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 22 comments
Labels: enhancement
#42 - Investigate ways to allow devs to handle fatal load errors
Issue -
State: open - Opened by unscriptable about 10 years ago
- 2 comments
Labels: enhancement
#41 - Document rave.overrides
Issue -
State: closed - Opened by KidkArolis about 10 years ago
- 2 comments
Labels: documentation
#40 - Make bower crawler more robust
Pull Request -
State: closed - Opened by KidkArolis about 10 years ago
- 22 comments
#39 - Bower should not use package.json as an alternate metadata file
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
#38 - Bower packages must be unversioned
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
#37 - Add support for browser field in package.json
Pull Request -
State: closed - Opened by KidkArolis about 10 years ago
- 20 comments
#36 - Add docs about using rave with AMD plugins.
Issue -
State: open - Opened by unscriptable about 10 years ago
Labels: documentation
#35 - Does not support AMD plugins.
Issue -
State: closed - Opened by treasonx about 10 years ago
- 7 comments
#34 - Per package loader configuration
Issue -
State: open - Opened by KidkArolis about 10 years ago
- 1 comment
#33 - Set npm package location to the root of the package
Pull Request -
State: closed - Opened by KidkArolis about 10 years ago
- 1 comment
#32 - Rave, webpack, browserify compatiblity
Issue -
State: open - Opened by KidkArolis about 10 years ago
- 1 comment
#31 - Bower quick start fails.
Issue -
State: closed - Opened by treasonx about 10 years ago
- 8 comments
#30 - Eliminating 404s
Pull Request -
State: closed - Opened by treasonx about 10 years ago
- 1 comment
#29 - A node builtins extension
Issue -
State: open - Opened by KidkArolis about 10 years ago
- 1 comment
#28 - Set npm and bower package location to the root of the package
Pull Request -
State: closed - Opened by KidkArolis about 10 years ago
- 6 comments
#27 - Avoiding 404s
Issue -
State: open - Opened by KidkArolis about 10 years ago
- 11 comments
#26 - Create a rave-start-react Starter?
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 15 comments
#25 - Add a CONTRIBUTING.md
Issue -
State: open - Opened by unscriptable about 10 years ago
Labels: documentation
#24 - Location and main of npm packages
Issue -
State: closed - Opened by KidkArolis about 10 years ago
- 4 comments
#23 - In npm packages use "browser" field as main if available
Pull Request -
State: closed - Opened by KidkArolis about 10 years ago
- 5 comments
#22 - Point newcomers at the new rave-start-* repos
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 1 comment
#21 - Defer missing dependency errors to factory execution time
Issue -
State: open - Opened by unscriptable about 10 years ago
#20 - Devise a way to help devs when they forget to use the `--save` option with npm or bower
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 8 comments
#19 - Some rave modules are loading twice
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 1 comment
#18 - Document the intended rave workflow and philosophy, as well as our roadmap
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
#17 - Provide more meaningful info when packages are misconfigured
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 1 comment
#16 - Rave overrides are only applied from the entry bower.json
Issue -
State: closed - Opened by phated about 10 years ago
- 6 comments
#15 - Encourage extension authors to include rave semver so we can inspect rave extensions for version compatibility when debugging
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
#14 - Reduce load extension non-determinism via metadata predicate specificity
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 2 comments
Labels: enhancement
#13 - Use the deployment pattern to load ES5 and/or ES6 shims
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 1 comment
#12 - Get rave working with TopCoat css
Issue -
State: closed - Opened by unscriptable about 10 years ago
- 3 comments
#11 - Make metadata crawling add main module path as module location
Pull Request -
State: closed - Opened by briancavalier about 10 years ago
- 1 comment
#10 - Resolve problems between rave's build script and cram 0.8.2
Issue -
State: open - Opened by unscriptable about 10 years ago
#9 - Create amd-plugin-to-rave loader hook extension
Issue -
State: closed - Opened by unscriptable over 10 years ago
- 2 comments
#8 - Process rave metadata key for package metadata overrides.
Pull Request -
State: closed - Opened by briancavalier over 10 years ago
- 2 comments
#7 - Allow devs to augment or override third-party packages' bower.json files
Issue -
State: closed - Opened by unscriptable over 10 years ago
- 12 comments
#6 - Refactor es5 pipelines to have a dedicated module registry
Issue -
State: open - Opened by unscriptable over 10 years ago
- 2 comments
#5 - Allow extensions to return undefined/falsy
Pull Request -
State: closed - Opened by briancavalier over 10 years ago
#4 - plugins aren't supported
Issue -
State: closed - Opened by phated over 10 years ago
- 6 comments
#3 - Modules in subdirectories aren't loaded correctly
Issue -
State: closed - Opened by phated over 10 years ago
- 4 comments
#2 - AMD require(array, callback) is busted
Issue -
State: closed - Opened by unscriptable over 10 years ago
- 3 comments
#1 - moduleType is an array of strings
Issue -
State: closed - Opened by unscriptable over 10 years ago