Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

remove require cache invalidation #5780

Merged
merged 4 commits into from
Dec 13, 2022
Merged

remove require cache invalidation #5780

merged 4 commits into from
Dec 13, 2022

Conversation

eggplantzzz
Copy link
Contributor

@eggplantzzz eggplantzzz commented Dec 12, 2022

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.

@eggplantzzz eggplantzzz changed the title remove require cache invalidation remove require cache invalidation Dec 12, 2022
@haltman-at
Copy link
Contributor

(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.)

Copy link
Member

@cds-amal cds-amal left a 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 () {
Copy link
Member

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?

Copy link
Contributor Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants