Ask us about:
- Maintaining OSS
- Contributing to OSS
- Plugin Ecosystem
Message from the host 💬
Thanks for participating and asking the questions!
If you want to get more involved:
- Follow us on Twitter: https://twitter.com/babeljs
- Join our Slack and participate in discussions like in #development: https://slack.babeljs.io/
- Add your company/library to our list of users (svg): http://babeljs.io/users
- Can start contributing by helping with our website: https://github.com/babel/website
- Check out https://github.com/babel/babel/blob/master/CONTRIBUTING.md
- Ask if you can sponsor us on Open Collective or with company time
- Make videos, tutorials, use (and talk) about Babel in posts, meetups, conference talks, etc.
- Note: none of us including the creator knew about compilers/ES6 when we started. It does take some time, but it's worth learning and contributing to!
How do you all manage to be so awesome?
How can one join the core maintainers team?
What are the biggest (technical and not technical) problems you are experiencing right now?
Compilers are something which I really want to learn about. Is there any good resources where I can learn about how Babel works?
When implementing a new spec, how closely does babel stick to it? Does it add any extra things to the feature?
Is there any talk about Babel being more involved in bundling? Babel already does a great job converting es6 imports to require but the bundling side has to defer to webpack/rollup/browserify. Would be great if one tool managed all this.
Babel was formerly called 6to5. How the name got changed?
Will Babel support workflow like autoprefixer - one will be able to define target support group "last 4 version" or "> 5%" and resulting transformations will reflect that?
Are you a robot?
How's your daily life while working on company and doing OSS project?
how crazy/feasible would it be to allow for different backends using babel? (e.g. wasm, llvm...) (assuming a runtime is included)
What do you think are qualities of a good maintainer (instead of a contributor/starter)?
What kind of proficiencies must an aspiring Babel core contributor aim to have?
How would you explain Babel to them?
How to prevent people from using non-standard / unstable plugins in production?
Which editors do you guys use to code?
Is the project formally sponsored? Are any of you formally sponsored? Would the project be at risk if it wasn’t sponsored?
Which upcoming spec features are you most excited about? pipe operator? observables (etc)?
Hi Awesome Babel team! What was the initial motivation behind creating Babel.js?
What's been your favorite experience/story from working on Babel?
Would you recommend newbies to learn and get comfortable with new stuff right away (promises, awaits, etc...) or go through established ways first?
Which module of Babel would you recommend first, if I needed to start contributing to Babel?
What are the tools you use to test the product?
How is your development lifecycle structured?
what is main scope of the babel project? how to organize your team? please tell your developing story of the project?
For a beginner like me who just knows that Babel can transpile ES6/7 to ES5, how can I get deep into the transpiling part of Babel.
Babel has support for few stage-0 proposals but not everything. How do you choose which feature to add to babel?
Babel adds bootstrap code to every single file which becomes repetitive across files. Is there any way to overcome this?
How can I get babel compiler logs when there is an error in compilation?
Hey! Any plans for compiling Typescript?
Is there any way to omit a commonly added plugin or preset under environment configuration in
babelrc file? Right now because of non common required in a particular environment, I have to copy all the common config to each environment.
The spec option in
babel-preset-env makes the transformation more spec complaint. But, not activating it will create any problems in how it works?
6to5 was an upstart competing with Google Closure Compiler and... Traceur, I think? Now it's the status quo. Do you foresee a smaller JS compiler coming along and having the same kind of success as Babel?
What was the last shell script you installed in your machine? 😀
I know this is off topic, but I am just curious.
When is Babel v7 releasing? What's the estimated date?
How does your team maintain such huge code base and most importantly how do you find time for this apart from the day job?
Why it's called Babel? What's the story!?
Why do you continue working on Babel? What makes maintaining a project worth the time/effort?
What's it like to do a release? (what's involved, hows the stress level, handling regressions, changelog, community feedback, semver, etc)
What does the
loose option in