Okay, I think I've resolved this so that custom config files will be honored as long as you put Babel into "I'll manage settings myself" mode in Project Settings, but I can't download your test project to verify because you didn't give me access. Maybe I got confused with this corejs option which is not for the same component at all. I'm sorry, I can neither remember nor find what it was exactly. However I cannot for the life of me remember where I saw that, but I think it was something about it using Core JS version 2 by default, and version 3 being preferable for some reason. It specifies which version of Core JS to use for the polyfills that Babel adds automatically with "usage" mode for preset-env. I'm doing that now, but I do not see a corejs option documented on babel-preset-env. Okay, so I think the easiest way to handle this will be to expand the UI options to allow this configuration. I don't know what would be relevant, but if I missed something, just ask. Your configuration (any details about your system that you think might be relevant) You'll notice that now, Babel won't polyfill your arrow functions at all anymore, because CodeKit ignores this file.Ī link to download a simplified project or file that shows the issue: You'll notice that Babel will have transpiled the arrow functions in YOUR code, but will have left those from vanilla-lazyload. Install, but do not import, the prerequisite modules.With CodeKit, everything is set up for you so you can get it up and running in no time at all. Other workflow wrappers have live updating, but they require extra configuration. i used to think that i would prefer //codekit-prepend and //codekit-append as i can keep compatibility with my collegues working with kodekit but these names //codekit-preppend and //codekit-append are not really generic. babelrc.) This is the standard Babel polyfilling process. CodeKit has live updating built in and will update monitored files across multiple browsers and devices, and refresh CSS without a new page load. Let's check that the rest of the process works properly by using. (Normally, this would be a file, but CodeKit ignores that. In project settings, tell CodeKit to use Babel -custom config files.In my case, the ES Module version of Vanilla Lazyload by verlok. Install and import a module that has an ES6 function you want to transpile.So it's impossible to transpile node_modules right now. babelrc, where empty exclude and import parameters do NOT affect node_modules. Normally, by mentioning empty array "exclude" and "ignore" settings in, you should be able to tell Babel to transpile and polyfill node_modules code, which is by default ignored by the process.ĬodeKit ignores. Since Babel 7, you're supposed to be able to ask Babel to also transpile imported node_modules, by using a file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |