Sourcemap shifting with multiline template strings in jest

[hjkcai]

Describe the bug
The sourcemap has shifting when testing in jest with multiline template strings. This problem will disappear after removing target option in swcrc.

See the screenshot below:

However, I cannot reproduce if I use swc cli directly. Everything seems be fine when I upload the source and the sourcemap to source-map-visualization. I have no idea whether this issue is related to jest or swc.

Input code

https://github.com/hjkcai/jest-swc-source-map-shifting

describe("foo", () => {
  it("test1", () => {
    expect(false).toBe(true);
  });

  it("test2", () => {
    const str = `
      bar
    `;

    expect(false).toBe(true);
  });

  it("test3", () => {
    expect(false).toBe(true);
  });
});

Config

{
  "sourceMaps": true,
  "jsc": {
    "target": "es2015"
  }
}

Expected behavior
The sourcemap correctly maps back to the source.

Version
The version of @swc/core: latest (1.2.83)

[ihm-tswow]

Looks like this is indeed an issue with swc, it also messes up sourcemaps for source-map-support with TypeScript.

The same thing also happens with multi-line comments:

/**
 * This is a
 * long
 * license
 * header
 */
console.log(new Error().stack)

Some findings:

• Single-line template strings (`string`) or multiline comments (/** comment */) are unaffected and work fine
• The issue more precisely seems to be that multiline comment / template string lines counts as two lines, for every new line i add to them, two are added to the output sourcemap.

@swc/cli: 0.1.52
@swc/core: 1.2.112

{
    "module": {
        "type":"commonjs"
    },
    "exclude":[".*.js$",".*\\.d.ts$"],
    "jsc": {
        "parser": {
            "syntax": "typescript",
            "tsx": false,
            "decorators": true,
            "dynamicImport": true
        },
        "target":"es2016",
    },
    "sourceMaps": true
}

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.