Prevent build issues when linking ember-source. #5339
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this, we used our ember-data's own dirname as the default
baseDir
for any of our custom babel plugins. This baseDir is used to traverse all JS files in all deps (recursively) and ensure that if any of them are changed, the transpilation cache is invalidated.Once we swapped to using ember-source as an npm package this meant that we would be stating/hashing all files inside of
node_modules/ember-source/**
. When usingnpm link ember-source
this leads to a JS max heap errors (because ofnode_modules/ember-source/tmp/**
being MASSIVE).This fixes that specific issue, by using the correct basedir for each individual plugin.
/cc @mmun