Access to atlassian-frontend source maps

Jira Development Jira Cloud
1

I can see source maps in Confluence Cloud, at least some of them, and I must admit that it is sometimes helpful:

  • debugging peculiarities of Confluence and Atlassian Connect
  • learning how Atlassian is using Atlaskit and React

There was a period, when source maps for Jira Cloud were also accessible, and it was great. Unfortunately as of today they are not accessible anymore (https://statlas.prod.atl-paas.net/ is not accessible from outside of Atlassian internal network).

Even without source maps I can still find answers to some of my questions, but it takes a lot of time, because the code is minified, and having access would speed up things in many aspects. Atlassian end users could benefit from that.

@dmorrow can you help here?

5 Likes
2

Hi @Grzegorz.Tanczyk,

I’m not across Jira source maps, but I’ll investigate.

Regards,
Dugald

4

Hi @Grzegorz.Tanczyk,

The Jira team decided to remove source maps to improve build times and security.

Regards,
Dugald

5

Interesting! Any ideas what was the gain in build times?

1 Like
6

I think it was ~20 minutes or so.

1 Like
7

@dmorrow I’m still not sure about this.

What is this security concern about? The source code is available anyway, just minified. Why Confluence Cloud team did not share this concern, and decided to publish source maps?

I can still see links to source maps in Jira Cloud frontend assets:

image
image1478×349 87.8 KB

If this file will open for you via Atlassian VPN: https://statlas.prod.atl-paas.net/jira-frontend-source-maps/assets/@atlaskit-internal_Clipboard.864f3faaa8537c1d9c3c.8.js.map it means that the source maps were not removed, and someone from Jira Cloud team is not giving a good answer.

Regardless of the above, WDYT about addressing those needs:

  • debugging peculiarities of Confluence and Atlassian Connect
  • learning how Atlassian is using Atlaskit and React

I thought that source maps is the cheapest way to achieve that, given that Jira Cloud guys are very busy (lots of work on the new issue view ahead of them ;))

2 Likes