Skip to content

environment specific builds #55

@subtleGradient

Description

@subtleGradient
  • node.js npm
  • mobile (iOS, Android, webOS, RIM, Windows 7 Mango+, Windows 8 Metro, Nokia N9, etc...)
  • desktop
  • legacy

The boilerplate HTML/RequireJS config for loading the correct build for the current environment should be a separate issue.

Should we also provide separate builds for legacy (no IE) and legacy (with old IE support)? The alternative would be to have a single legacy build with the workarounds for all old browsers. Worst case would be delivering extra bytes to old Opera, Firefox and Safari.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions