chore: Remove memory-tests

[nschonni]

Just noticed these when I trying opening up the ESLint globs. These look specific to the work down in 4.7 memory performance stuff. Since we don't actually run this as part of any part of the build process I think they can be dropped.

[xzyfer]

Let's keep these. I'm using them now for the N-API work to prevent regressions.

…

On Mon., 9 Jul. 2018, 4:37 pm Nick Schonning, ***@***.***> wrote: Just noticed these when I trying opening up the ESLint globs. These look specific to the work down in 4.7 memory performance stuff. Since we don't actually run this as part of any part of the build process I think they can be dropped. ------------------------------ You can view, comment on, or merge this pull request online at: #2442 Commit Summary - chore: Remove memory-tests File Changes - *D* memory-tests/_measure.js <https://github.com/sass/node-sass/pull/2442/files#diff-0> (12) - *D* memory-tests/boolean.js <https://github.com/sass/node-sass/pull/2442/files#diff-1> (6) - *D* memory-tests/function-bridge.js <https://github.com/sass/node-sass/pull/2442/files#diff-2> (15) - *D* memory-tests/map.js <https://github.com/sass/node-sass/pull/2442/files#diff-3> (17) - *D* memory-tests/string.js <https://github.com/sass/node-sass/pull/2442/files#diff-4> (6) Patch Links: - https://github.com/sass/node-sass/pull/2442.patch - https://github.com/sass/node-sass/pull/2442.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2442>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWFlNMLP8lg99nM80zRz-2UD6Cnyoks5uEvoOgaJpZM4VHJ38> .