fix: replace backslashes with forward slashes from resolved path for …

[johannes-z]

…windows environments

Q	A
Fixed Issues?	Fixes #11357
Patch: Bug Fix?	Yes
Major: Breaking Change?	No
Minor: New Feature?	No
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?	No
License	MIT

See #11357

[nicolo-ribaudo]

@johannes-z Could you add a test for this change?

Since the test should only run on windows, you can specify it like it has been done in packages/babel-plugin-transform-react-jsx-development/test/fixtures/windows/classic-runtime-with-source-self-plugins-windows/options.json.

[johannes-z]

@nicolo-ribaudo Sure, I can try. I have no experience with the test suite. Are there docs for it? I also would need to know how to run it 😓

[existentialism]

@johannes-z check out https://github.com/babel/babel/blob/master/CONTRIBUTING.md#running-lintingtests, and let us know if you run into any problems so we can improve the docs!

Also, feel free to join our Slack if you need any help!

[johannes-z]

I'm on Windows here and unable to run the test suite:

$ make test
BABEL_ENV=test yarn --silent eslint scripts packages codemods eslint '*.js' --format=codeframe
'BABEL_ENV' is not recognized as an internal or external command,
operable program or batch file.
mingw32-make: *** [Makefile:112: lint-js] Error 1

[nicolo-ribaudo]

Try running yarn jest directly.

[johannes-z]

It worked executing, but I'm getting errors:

 FAIL  packages/babel-plugin-transform-typescript/test/index.js
  ● Test suite failed to run

    Configuration error:

    Could not locate module @babel/code-frame mapped as:
    ......\babel\packages\babel-code-frame.

    Please check your configuration for these entries:
    {
      "moduleNameMapper": {
        "/^@babel\/(?!eslint-)(?!plugin-syntax-async-generators|plugin-syntax-bigint|plugin-syntax-dynamic-import|plugin-syntax-json-strings|plugin-syntax-nullish-coalescing-operator|plugin-syntax-object-rest-spread|plugin-syntax-optional-catch-binding|plugin-syntax-optional-chaining|plugin-syntax-export-namespace-from)([a-zA-Z0-9_-]+)$/": "......\babel\packages\babel-$1"
      },
      "resolver": null
    }

      at createNoMappedModuleFoundError (node_modules/jest-resolve/build/index.js:501:17)

---

Ok nevermind, I figured it out. The docs should be improved a little for windows. It's quite hard to figure out how everything works if you're not familiar with the project setup:

yarn lerna bootstrap
yarn gulp build
yarn jest babel-plugin-transform-runtime

Now it works.

[nicolo-ribaudo]

@johannes-z We are thinking about migrating away from make to make it easier for windows users.

[nicolo-ribaudo]

Thanks for the patch anyway!