You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across an error about 3 layers abstracted from this repository but a simple configuration change to the deployment would prevent issues with support of newer configurations.
My error occurs within DevExpress/testcafe when evaluating a testcase in es2017 javascript. When a testcase is run, it is transposed via Babel prior to execution. Your package is used by @Babel/core@7. During the babel compilation step, your package processed and it processes your test/index.test.ts which has an unresolved module.
This looks like an old implementation of require() that is no longer valid in Node@>=10.24.
I can't figure out why Babel is transpiling the entire module rather than just your package.json[main]. I figure this is an easy fix to just prevent your test code from being included in your package which is likely unintentional.
FYI, New updates in npmv6 & 7 have helped ensure smaller production packages through the use of the files directive.
The text was updated successfully, but these errors were encountered:
I came across an error about 3 layers abstracted from this repository but a simple configuration change to the deployment would prevent issues with support of newer configurations.
My error occurs within DevExpress/testcafe when evaluating a testcase in es2017 javascript. When a testcase is run, it is transposed via Babel prior to execution. Your package is used by
@Babel/core@7
. During the babel compilation step, your package processed and it processes yourtest/index.test.ts
which has an unresolved module.This is the error I get:
I dug through the code and found this is because of:
This looks like an old implementation of
require()
that is no longer valid inNode@>=10.24
.I can't figure out why Babel is transpiling the entire module rather than just your
package.json[main]
. I figure this is an easy fix to just prevent your test code from being included in your package which is likely unintentional.FYI, New updates in npmv6 & 7 have helped ensure smaller production packages through the use of the
files
directive.The text was updated successfully, but these errors were encountered: