# "Failed to parse source map" errors with datetime picker and CRA5

**URL:** <https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562>\
**Category:** Atlassian Ecosystem Design\
**Tags:** react, sourcemap, atlaskit\
**Created:** [April 14, 2022, 11:13pm UTC](https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562 "2022-04-14T23:13:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![OllyHodgson](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ollyhodgson/32/45021_2.png) [@OllyHodgson](https://community.developer.atlassian.com/u/OllyHodgson)\
**Post date:** [April 14, 2022, 11:13pm UTC](https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562/1 "2022-04-14T23:13:51Z")

</div>

Hello,

When using the Atlaskit DateTimePicker components in my Create React App 5.0.0 app, I get warnings about missing sourcemaps in @atlaskit/analytics-next-stable-react-context:

```auto
Failed to parse source map from '/repos/projectname/node_modules/@atlaskit/analytics-next-stable-react-context/src/context.ts' file: Error: ENOENT: no such file or directory, open '/repos/projectname/node_modules/@atlaskit/analytics-next-stable-react-context/src/context.ts'

Failed to parse source map from '/repos/projectname/node_modules/@atlaskit/analytics-next-stable-react-context/src/index.ts' file: Error: ENOENT: no such file or directory, open '/repos/projectname/node_modules/@atlaskit/analytics-next-stable-react-context/src/index.ts'

```

They’re an annoyance, but short of ejecting or using something like CRACO I can’t see a way to get rid of them. Is there any chance this’ll get fixed up soon?

Thank you!

---

<div class="post-metadata">

**Author:** ![DillonRice](https://avatars.discourse-cdn.com/v4/letter/d/74df32/32.png) [@DillonRice](https://community.developer.atlassian.com/u/DillonRice)\
**Post date:** [May 18, 2022, 8:48pm UTC](https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562/2 "2022-05-18T20:48:00Z")

</div>

Did you ever get an answer for this? Running into the same issue.

---

<div class="post-metadata">

**Author:** ![OllyHodgson](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ollyhodgson/32/45021_2.png) [@OllyHodgson](https://community.developer.atlassian.com/u/OllyHodgson)\
**Post date:** [May 25, 2022, 9:17pm UTC](https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562/3 "2022-05-25T21:17:08Z")

</div>

I did not. I found a way to suppress the warnings using [GitHub - jhnns/rewire: Easy monkey-patching for node.js unit tests](https://github.com/jhnns/rewire), but it feels a bit hacky.

I’ve run into other limitations with this datetime picker (e.g. no obvious way for the user to skip to another year), so I’m now looking for an alternative.

---

<div class="post-metadata">

**Author:** ![OllyHodgson](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ollyhodgson/32/45021_2.png) [@OllyHodgson](https://community.developer.atlassian.com/u/OllyHodgson)\
**Post date:** [May 31, 2022, 5:31pm UTC](https://community.developer.atlassian.com/t/failed-to-parse-source-map-errors-with-datetime-picker-and-cra5/57562/4 "2022-05-31T17:31:52Z")

</div>

I forgot to say, in the short term I’ve disabled sourcemap generation. I’ve updated my package.json as follows:

`"start": "GENERATE_SOURCEMAP=false yarn react-scripts start",`

Funnily enough, the [CRA documentation suggests it’s ignored in development](https://create-react-app.dev/docs/advanced-configuration). It’s really not ideal, but it works 🤷‍♂️