BREAKING: expose getTransformOptions directly in configuration

Summary:
Instead of exposing a `getTransformOptionsModulePath` function in configurations, we can simply expose a `getTransformOptions` *function*. The necessity of exposing a path comes from the olden days, where we had a server listening on a socket, and a client, talking to that server.

Since that architectural gem no longer exists, we can use functions directly, rather than passing paths to modules around.

Reviewed By: cpojer

Differential Revision: D4233551

fbshipit-source-id: ec1acef8e6495a2f1fd0911a5613c144e8ffd7c3
This commit is contained in:
David Aurelio authored and Facebook Github Bot committed 2016-11-28 07:28:33 -08:00
1 parent c197c49123
commit 8ad2ab3b5e
7 files changed
+16 -19

No files matched your search

+1 -1
View File
@@ -90,7 +90,7 @@ function getPackagerServer(args, config) {
blacklistRE: config.getBlacklistRE(),
cacheVersion: '3',
extraNodeModules: config.extraNodeModules,
getTransformOptionsModulePath: config.getTransformOptionsModulePath,
getTransformOptions: config.getTransformOptions,
projectRoots: args.projectRoots,
resetCache: args.resetCache,
transformModulePath: transformModulePath,