-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Conversation
…e - and unused Module import
require
cache invalidation
(I changed the labels on this, the "requires-breaking-change" label is for issues that would require a Truffle breaking change; PRs that break a particular package should be marked with the appropriate label for that package.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
@@ -11,12 +11,9 @@ describe("config", function () { | |||
let output = ""; | |||
let memStream; | |||
|
|||
before(function () { | |||
beforeEach(function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clearing the cache allowed this to pass before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so - I think the complications arose from the order in which Config
merges in changes in load
THIS IS A BREAKING CHANGE FOR @truffle/config.
So #5728 brought to our attention the fact that this cache invalidation does not work in the bundle (since
require
in this case is webpack's and not Node's). This PR deletes this line of code until we decide that we actually need to invalidate Node's cache.