Skip to content

fullPaths should be configurable #107

@timiyay

Description

@timiyay

I've just started experimenting with ember-browserify, and I've come across an issue where my built files leak system paths, such as in this issue: browserify/browserify#902

This library hardcodes the fullPaths option to true, for any non-production environments.

I need this to be configurable, as I use a staging environment, which should be treated like production in most respects.

Ideally, I would be able to use this library's existing config to do this, like so:

// config/environment.js
// (or wherever this config ends up: https://github.com/ef4/ember-browserify/issues/96)
var isProductionLikeBuild = ['production', 'staging'].indexOf(EmberApp.env()) > -1;

browserify: {
  fullPaths: !isProductionLikeBuild,
  extensions: ['.coffee'],
  transform: [
    ['caching-coffeeify', { global: true }]
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions