So for the most part things are working well.
It looks like there is an issue with the source maps when using chrome.
I made two test files:
`numbers.es6.js`
~~~~~
::javascript
//numbers.es6.js
[1,2,3].forEach(function(n){
console.log(`${n} is a number`);
});
console.log('I was called from "numbers"');
~~~~~
and `letters.es6.js`
~~~~~
::javascript
//letters.es6.js
["a", "b", "c"].forEach(function (n) {
console.log(`${n} is a letter`);
});
console.log('I was called from "letters"');
~~~~~
The output is here:
Chrome seems to get confused about where things are coming from.
Attachments:
-
[es6_map_chrome.png](https://forge-allura.apache.org/p/allura/tickets/_discuss/thread/94e7871a/f14b/attachment/es6_map_chrome.png)
(70.2 kB; image/png)
---
** [tickets:#7976] JSX support**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-current sf-2
**Created:** Mon Aug 24, 2015 02:54 PM UTC by Dave Brondsema
**Last Updated:** Wed Sep 30, 2015 08:04 PM UTC
**Owner:** Dave Brondsema
We may need JSX support for [#7920] If so, we'll need to configure things like:
* JSX compiling for development (with minimal dependencies added)
* step-by-step instructions
* Docker setup
* script or something to run it for final "production-ready" output
* run that script during `asf-release.sh` so that our releases don't require
JSX tools to be installed
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
