Closed timiyay closed 5 years ago
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: https://github.com/substack/node-browserify/issues/902
ember-browserify
This library hardcodes the fullPaths option to true, for any non-production environments.
fullPaths
true
I need this to be configurable, as I use a staging environment, which should be treated like production in most respects.
staging
production
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 }] ] }
PR submitted: https://github.com/ef4/ember-browserify/pull/108
Closing this issue as stale.
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: https://github.com/substack/node-browserify/issues/902This library hardcodes the
fullPaths
option totrue
, for any non-production environments.I need this to be configurable, as I use a
staging
environment, which should be treated likeproduction
in most respects.Ideally, I would be able to use this library's existing config to do this, like so: