build a distributed bundle about mapbox-gl-accessibility

[allthesignals]

@marharyta I also am working on a few city projects, getting the same issue here.

I'll take a look and see if we can get it building!

[allthesignals]

@tristen you bet! as soon as that's merged i'll PR a simple test suite so we can refactor stuff.

[tristen]

Arrow functions were introduced in ES6!

[andrewharvey]

Thanks, With that in mind, I'll try a bit more to see if I can get it transpiling into a distributable build.

[marharyta]

@andrewharvey what is the situation with that? I am currently building an app that might critically need good a11y (city project) and I want to know if there is any CDN I can use? Thanks a lot for your work! Also, do you need help? I am not good with maps but I can try!

[andrewharvey]

@marharyta I'm not working on this at the moment, so feel free to give it a go yourself. You can take a look at a similar project https://github.com/mapbox/mapbox-gl-draw/blob/master/package.json and see how it generates the dist build and try to replicate that here?

[allthesignals]

I am also running into this syntax error. Babel doesn't seem to be seeing this plugin: https://babeljs.io/docs/en/next/babel-plugin-proposal-class-properties.html

When I change the syntax from the arrow function style syntax to class method syntax (myProp = () => { } to myProp(){ }), I'm able to build; Babel can transform without issue.

There is a slight difference, but not relevant here. That said, I will keep trying to see why arrow function methods aren't working (I'd rather understand why this wasn't working in the first place than work around). Oops, it is relevant. These are event callbacks :) so binding matters.

Fork here until I get something ready for PR: https://github.com/allthesignals/mapbox-gl-accessibility

[allthesignals]

What are some next steps for this? I want to help but I'm not sure what needs to happen to publish this onto npm and a CDN? I'm assuming this will need to happen on Mapbox's account...

[tristen]

👋 @allthesignals I can help with the publish step to npm. OK to do that when #34 is merged?