Async functions are always transformed to regenerator runtime #871

aocenas · 2018-02-20T21:11:17Z

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

Without config just do

yarn init
yarn add parcel-bundler

create index.js:

(async function () { return await 1 })()

parcel index.js

🤔 Expected Behavior

Without any babel config I would assume no transformation will be made, just bundling into one file.

😯 Current Behavior

Dist file will contain

_asyncToGenerator( /*#__PURE__*/regeneratorRuntime.mark(function _callee() {
...

💁 Possible Solution

🔦 Context

In specific project async functions are transformed no matter what .babelrc I try. I am trying to migrate from browserify but using

node_modules/.bin/parcel build ./src/client/index.js --out-dir ./public --out-file bundle.js --no-minify

will give me code with async functions transformed, where

node_modules/.bin/browserify ./src/client/index.js -o ./public/bundle.js -t [ babelify ]

will keep async functions unchanged. I would expect these to behave the same in regards to babel transforms.

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	1.6.2
Node	v8.1.4
npm/Yarn	1.3.2
Operating System	Mac

The text was updated successfully, but these errors were encountered:

aocenas · 2018-02-20T21:13:56Z

Seems like it could be related to #509 somehow, but no-cache does not help and I did not have any async transform set up anywhere.

devongovett · 2018-02-20T21:22:37Z

Parcel automatically applies babel-preset-env to some default engines (> 1% marketshare). You can change your app's browser targets by adding a browserslist key to your package.json.

aocenas · 2018-02-20T21:45:16Z

@devongovett Thanks for quick reply. As you say using env preset and specific targets helped. Sorry, this was not clear to me from the documentation and is a bit confusing when having a .babelrc defined. I would still assume that defining .babelrc would override the default transforms, while at the moment it seems it is merging them in some sense.

davidnagli · 2018-02-22T17:06:04Z

@aocenas That’s a good point. If you want, feel free to open up an issue in the website repo so it get’s added to the docs 👍

AbeEstrada · 2018-02-23T03:29:35Z

I was getting this error when using async/await:
ReferenceError: regeneratorRuntime is not defined

My solution was adding: import "babel-polyfill";

Leaving this comment for reference.

silvestrevivo · 2018-03-01T21:50:05Z

Here my solution:
npm install --save-dev babel-plugin-transform-runtime
And in .babelrc
{ "plugins": ["transform-runtime"] }

brandiqa · 2018-03-03T09:52:03Z

Found this solution:

npm install --save-dev babel-plugin-transform-runtime babel-runtime

Create .babelrc file and add:

{
    "plugins": [
        ["transform-runtime",
        {
            "polyfill": false,
            "regenerator": true
        }]
    ]
}

silvestrevivo · 2018-03-03T10:59:57Z

@brandiqa that solutions looks like very similar to mine but more complete. That is nice!!

NullVoxPopuli · 2018-05-03T15:28:17Z

@brandiqa this doesn't seem to work when typescript is involved.

tsconfig.json

{
  "compilerOptions": {
    "jsx": "react",
    "experimentalDecorators": true,
    "lib": ["es2017", "dom"],
    "target": "es2018",
    "baseUrl": ".",
    "paths": {
      "react": ["node_modules/@types/react/index.d.ts"],
      "redux": ["node_modules/redux/index.d.ts"],
      "react-toastify": ["node_modules/react-toastify/index.d.ts"]
    }
  }
}

I get this error:

Building index.tsx...
ui_1          | 🚨  /app/src/index.tsx: Unknown plugin "transform-runtime" specified in "base" at 0, attempted to resolve relative to "/app/src"
ui_1          |     at /app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
ui_1          |     at Array.map (<anonymous>)
ui_1          |     at Function.normalisePlugins (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
ui_1          |     at OptionManager.mergeOptions (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
ui_1          |     at OptionManager.init (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
ui_1          |     at File.initOptions (/app/node_modules/babel-core/lib/transformation/file/index.js:212:65)
ui_1          |     at new File (/app/node_modules/babel-core/lib/transformation/file/index.js:135:24)
ui_1          |     at TypeScriptAsset.getParserOptions (/app/node_modules/parcel-bundler/src/assets/JSAsset.js:69:20)
ui_1          |     at <anonymous>

{
  "name": "react-parcel-test",
  "version": "1.0.0",
  "license": "MIT",
  "scripts": {
    "start": "./node_modules/.bin/parcel src/index.html --hmr-port $HMR_PORT -p $PORT",
    "dev": "./node_modules/.bin/ts-node src/dev-server.ts"
  },
  "dependencies": {
    "react": "^16.3.2",
    "react-dom": "^16.3.2",
    "react-state-helpers": "^1.6.6",
    "react-toastify": "^4.0.1"
  },
  "devDependencies": {
    "@types/express": "^4.11.1",
    "@types/http-proxy-middleware": "^0.17.4",
    "@types/node": "^10.0.3",
    "@types/react": "^16.3.13",
    "@types/react-dom": "^16.0.5",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-runtime": "^6.26.0",
    "express": "^4.16.3",
    "http-proxy-middleware": "^0.18.0",
    "parcel-bundler": "^1.7.1",
    "ts-node": "^6.0.2",
    "typescript": "^2.8.3"
  }
}

theoutlander · 2018-05-17T03:34:11Z

I had accidentally set the config value to:

"plugins": [
    [
      "transform-object-rest-spread",
      "syntax-dynamic-import",
      "transform-runtime",
      {
        "polyfill": false,
        "regenerator": true
      }
    ]
  ]

Changing it to the following worked for me:

"plugins": [
    "transform-object-rest-spread",
    "syntax-dynamic-import",
    [
      "transform-runtime",
      {
        "polyfill": false,
        "regenerator": true
      }
    ]
  ]

janat08 · 2018-09-10T13:30:01Z

Perhaps the runtime transform should be default?

wesbos · 2019-01-09T17:21:35Z

I run into this all the time with demos - so if you want to just ignore this error and use the browsers built in async/await I use this for a quick fix without having to install any babel plugins:

"browserslist": [
    "last 1 Chrome version"
  ],

thedamon · 2019-01-10T03:44:19Z

Is this supposed to work somehow without babel-polyfill?

I tried all the .babelrc plugin settings to no avail.. babel-polyfill did it, but it's a pretty heavy dependency to make something work that actually works natively in all evergreen browsers now

gcv · 2019-01-13T18:48:25Z

@thedamon: I didn't want to use babel-polyfill either, but @wesbos's suggestion of using browserslist works well. I added the following to package.json:

  "browserslist": [
    "since 2017-06"
  ],

Cody0913 · 2019-01-22T18:54:04Z

Just an update to @brandiqa solution for those with a babel version of 7^.
The polyfill option has been removed from the transform-runtime plugin has been removed and is now just the following:
["@babel/plugin-transform-runtime", { "regenerator": true } ]

thedamon · 2019-01-23T17:23:15Z

@gcv.. yeah that would work for a lot of users.. i think i just wish there was a way to use async/await simply and still support IE11.. kinda the point of babel.. but without needing the babel-polyfill on all sites because it's like 300k and that's nuts. currently i can't make it work in Chrome without babel-polyfill and that actually makes no sense because it shouldn't be necessary because it shouldn't have anything to polyfill.

but this applies to babel moreso than parcel so i'll stick a lid on it 😋

shandou · 2019-02-04T06:25:48Z

I was getting this error when using async/await:
ReferenceError: regeneratorRuntime is not defined

My solution was adding: import "babel-polyfill";

Leaving this comment for reference.

I am getting the same error and this solution works for me.

adrianmcli · 2019-02-10T05:59:00Z

@thedamon Does adding @babel/plugin-transform-runtime work for you? Or does it also bloat the production build?

Limiting to recent browsers because of: parcel-bundler/parcel#871

MarvelousWololo · 2019-07-26T16:53:07Z

I love how after one year and a half we still don't have a definitive answer to this question. Every solution here includes adding a bunch of dependencies to your project and stopping doing that when the issue actually ceases or seems to be solved.

Gotta love modern JS tooling. It's 2019 and we are struggling to do a simple HTTP request. On the web. <3

adrianmcli · 2019-07-29T17:03:44Z

@mischnic Thanks for re-opening! Hope we can come to a solution to improve UX for Parcel users everywhere :)

TempD · 2019-08-01T02:21:50Z

Just want to leave a note and say that my code worked with this fix now. Running Babel core 7.7.5. Here is my .babelrc:

{
    "presets": ["@babel/preset-react"],
    "plugins": [
        [
            "@babel/plugin-transform-runtime",
            { "regenerator": true }
        ]
    ]
}

Just an update to @brandiqa solution for those with a babel version of 7^.
The polyfill option has been removed from the transform-runtime plugin has been removed and is now just the following:
["@babel/plugin-transform-runtime", { "regenerator": true } ]

wangcch · 2019-08-28T11:06:46Z

Premise: typescript and no babel

I was also getting this error when using async/await:
ReferenceError: regeneratorRuntime is not defined

My solution is to change tsconfig target:

// tsconifg.json
{
  "compilerOptions": {
    "target": "es5",
    ...
  },
  ...
}

For reference

adrianmcli · 2019-08-29T08:01:30Z

Just want to leave a note and say that my code worked with this fix now. Running Babel core 7.7.5. Here is my .babelrc:
{
    "presets": ["@babel/preset-react"],
    "plugins": [
        [
            "@babel/plugin-transform-runtime",
            { "regenerator": true }
        ]
    ]
}
Just an update to @brandiqa solution for those with a babel version of 7^.
The polyfill option has been removed from the transform-runtime plugin has been removed and is now just the following:
["@babel/plugin-transform-runtime", { "regenerator": true } ]

This works, but we shouldn't need to do this in 2019.

rosman21 · 2019-10-14T15:03:20Z

Just want to leave a note and say that my code worked with this fix now. Running Babel core 7.7.5. Here is my .babelrc:
{
    "presets": ["@babel/preset-react"],
    "plugins": [
        [
            "@babel/plugin-transform-runtime",
            { "regenerator": true }
        ]
    ]
}
Just an update to @brandiqa solution for those with a babel version of 7^.
The polyfill option has been removed from the transform-runtime plugin has been removed and is now just the following:
["@babel/plugin-transform-runtime", { "regenerator": true } ]
This works, but we shouldn't need to do this in 2019.

what other options do we have?

corwin-of-amber · 2019-11-07T17:09:48Z

what other options do we have?

All major browsers and Node.js have had async/await support for about two years now.
I have found that setting "browserslist": ["since 2017-06"] in package.json does not turn off the regenerator transform in babel, but e.g. "browserslist": ["Chrome 78"] does.

Rollup requires additional configuration for electron to work. I'm not sure this is the best way of doing it, but it at least works now. For reference, here are the relevant resources: - https://github.com/rollup/rollup-plugin-babel#helpers - https://babeljs.io/docs/en/babel-plugin-transform-runtime#regenerator - parcel-bundler/parcel#871 (comment) - babel/babel#8829 (comment) - rollup/rollup#3160 - rollup/rollup-plugin-babel#209 (comment)

* Extend schema for project creation * Keep GraphQL schema in sync with mock implementation * Extract layouts in preparation for modal implementation * Add create project modal * Add help page and keyboard shortcuts to access design system * Tweak design system * Fix spec * Use library for hotkeys This lib gracefully handles ignoring hotkeys while focusing on inputs. * Add disabled dropdown variant * Add CheckboxInput * Disable default branch dropdown by default * Use electron's open dialog for directory input This allows us to select empty directories, which is not possible with a plain input with type "file" in a regular browser environment, as it doesn't fire any events when empty directories are chosen. * Fixup for directory input Rollup requires additional configuration for electron to work. I'm not sure this is the best way of doing it, but it at least works now. For reference, here are the relevant resources: - https://github.com/rollup/rollup-plugin-babel#helpers - https://babeljs.io/docs/en/babel-plugin-transform-runtime#regenerator - parcel-bundler/parcel#871 (comment) - babel/babel#8829 (comment) - rollup/rollup#3160 - rollup/rollup-plugin-babel#209 (comment) * Improve css class naming * Show placeholder if path is not present * Make localBranches query consistent with the branches query * Add validations Disable button if form is not complete (name or path missing) and show validation messages for name. * Remove unneeded attribute * Add librad dependency * Set up mutation testing scaffold * Add missing gql queries * Create temp dir for project init test * Make focussed input outline color customisable * Make focussed select outline color customisable * Wire up repo and rad project creation * Port old design system page layout over from Reason prototype * Init repo in create project mutation * Isolate paths dir per environment * Remove test flag from proxy start * Modularise schema * Complete create project mutation * Use actual ID scalar for project id * Move repo init helper to git module * Remove source from context * Show notification after creating project * Add project avatar input * Start project query rewrite to librad * Complete project list testing * Add publish field to project creation * Bring back project query * Test project endpoint * Replace IdInput with ID for all queries * Revert back to using id instead of name/domain pair * Reintroduce test projects when flag is passed * Implement local branches query * Attach open dialog to the main window So it doesn't go to background after creating a new folder. * Fix create mutation * Keep temp dir in scope for proxy test mode * Fix navigation spec It was broken because we changed the page layout. * Fix source browsing tests The breakage was related switching to a hash address as opposed to domain/name. * Fix relative time tests The clock has to be frozen before the test setup is run. * Add missing hotkey description * Use the correct query for local branch fetching * Show notifications longer * Reset local branch dropdown and message on failure * Update fixture repo * Fix active selection border * Address clippy feedback * Install clippy for nightly toolchain * Please the clippy * Animate choosing an option * Use more concise find_map * Add documentation about why we use electron open dialog * Add more descriptive section name for notifications * Use routing strings from path.js * Use more appropriate variable type * Use only one modifier key for now * Unbreak my build Co-authored-by: Alexander Simmerl <a.simmerl@gmail.com>

danielfilho · 2020-02-02T20:57:48Z

I have tried every single solution (and many combinations of those) in this whole thread and none seems to work for me (except the ones related to TypeScript, as it's not my case) 😞

I can supply more information if needed, just ask it to me and I'll be able to do so.

corwin-of-amber · 2020-02-03T13:21:55Z

@danielfilho Are you using the latest version of @babel/core? I just tried with 7.8.4 and it still works as long as you include the "browserslist": ["Chrome 78"] in your package.json (without it it still breaks).

danielfilho · 2020-02-03T14:52:46Z

these are the versions I'm using:

 "devDependencies": {
    "@babel/core": "7.2.0",
    "@babel/preset-env": "^7.4.3",
    "babel-jest": "^24.7.1",
    "jest": "^24.7.1",
    "parcel-bundler": "^1.6.1"
  }

Locally, I was trying to update all dependencies to the latest but the problem was still there. Even cleaning node_modules and npm cache.

I solved this giving up on doing locally and moving the development to codesandbox.io, which is far from ideal. But at least I could move on with the project.

I know how weird it sounds, but I tried everything, and then gave up to this solution. Thanks for asking, @corwin-of-amber.

corwin-of-amber · 2020-02-03T15:38:01Z

@danielfilho I am attaching a minimal code example that shows the problem so that you and other users visiting this issue could perhaps use to troubleshoot.

Notice how removing browserslist from package.json causes the error (Can't find variable: regeneratorRuntime).

generator-minimal.zip

jcs224 · 2020-02-25T22:18:13Z

Thought I'd throw this in, as this seems like the most "correct" way (serious air quotes here) based on what seems like best practice in Babel and what actually ended up working for me:

Install the plugin transform runtime

npm install --save-dev @babel/plugin-transform-runtime

Add this to your .babelrc file

{
  "plugins": ["@babel/plugin-transform-runtime"]
}

I didn't include the runtime or configure any options. Parcel must do this magic? I'm using a Chromium-based browser so I don't know how this works on older browsers, but it fixed this immediate issue for me. Followed the instructions outlined here:

https://babeljs.io/docs/en/babel-plugin-transform-runtime#with-a-configuration-file-recommended

This was originally added to resolve issues with Parcel's default handling of async functions: parcel-bundler/parcel#871 There's no usage of `async` in this codebase anymore, so it's not necessary to have it (removing it will allow babel to polyfill some ES6 functionality for old browsers).

…ler/parcel#871

zavan · 2020-05-13T15:36:46Z

This may be helpful for those that need to make it work with old browsers (e.g.: with the default (or no) browserslist): #1762 (comment)

The issue is that the dependency regenerator-runtime/runtime needs to be bundled with the rest of your code to make it work on the browser, and Parcel doesn't do that by default.

Workaround from parcel-bundler/parcel#871 (comment) .

corwin-of-amber · 2020-11-10T15:02:48Z

Seems like this is not fixed (as the workaround from 11/8/2020 shows?), is it no longer an issue in Parcel 2.0.0?

mischnic · 2020-11-10T15:32:16Z

Re "Async functions are always transformed to regenerator runtime":
This is intentional, as the default browserslist simply contains browsers that don't support await/async. Async functions are always transformed to regenerator runtime #871 (comment)
Re "Uncaught ReferenceError: regeneratorRuntime":
See Uncaught ReferenceError: regeneratorRuntime #1762 (comment).

corwin-of-amber · 2020-11-10T15:35:01Z

Re "Uncaught ReferenceError: regeneratorRuntime":
See #1762 (comment).

Great! Thanks for adding this reference for anyone who encounters this error in the future.

See more details here: - https://flaviocopes.com/parcel-regeneratorruntime-not-defined/ - parcel-bundler/parcel#2128 - parcel-bundler/parcel#871

davidnagli closed this as completed Feb 22, 2018

ryanmurakami mentioned this issue Mar 5, 2018

Parcel upgrade to 1.6.x propelml/propel#322

Closed

CompuIves mentioned this issue Mar 22, 2018

Can't find variable: regeneratorRuntime codesandbox/codesandbox-client#656

Closed

philipjscott mentioned this issue Apr 13, 2018

feat(render): Add UI logic for rendering payload jpngfile/crumbs#19

Merged

gallayl mentioned this issue May 17, 2018

Research: parceljs SenseNet/sn-document-viewer-react#15

Closed

13 tasks

AlexEngblom added a commit to Majavapaja/Majavashakki that referenced this issue Oct 21, 2018

Fix parcel babel shit with async syntax: parcel-bundler/parcel#871

9b4d8f0

steren mentioned this issue Nov 13, 2018

regeneratorRuntime is not defined error when running the posenet demo tensorflow/tfjs#904

Closed

Cody0913 mentioned this issue Jan 22, 2019

"regeneratorRuntime is not defined" error with async and "useBuiltIns": "usage" babel/babel#8829

Closed

elorzafe mentioned this issue Jan 26, 2019

regeneratorRuntime is not defined aws-amplify/amplify-js#2598

Closed

williaster mentioned this issue Mar 14, 2019

Issue in using superset react plugins in angular app apache-superset/superset-ui-plugins#20

Open

foobarbecue added a commit to foobarbecue/splor that referenced this issue Mar 31, 2019

Lay groundwork for rosbag support (#1)

3c95beb

Limiting to recent browsers because of: parcel-bundler/parcel#871

mischnic added 🐛 Bug Babel labels Jul 29, 2019

FlorianRappl mentioned this issue Jan 3, 2020

Large Bundles Run Out Of Memory smapiot/piral#121

Closed

3 tasks

tsukhu mentioned this issue Jan 15, 2020

sample-piral example does not work on the Edge Browser smapiot/piral#128

Closed

3 tasks

jsonkao added a commit to graphicsdesk/ivy-coronavirus-response that referenced this issue Apr 8, 2020

just use browserslist instead of babel transform runtime. parcel-bund…

3c395d9

…ler/parcel#871

angelocordon mentioned this issue Apr 26, 2020

Update Jest to 25.4 codebuddies/frontend#106

Merged

gustavodemorais mentioned this issue Aug 6, 2020

Run frontend code without server.js tmcw/geojson.net#63

Closed

lgarron added a commit to cubing/cubing.js that referenced this issue Nov 8, 2020

Fix regenerator-runtime errors in Parcel builds.

6af7a19

Workaround from parcel-bundler/parcel#871 (comment) .

github-actions bot added the Stale Inactive issues label Nov 10, 2020

github-actions bot removed the Stale Inactive issues label Nov 10, 2020

mischnic closed this as completed Nov 10, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Async functions are always transformed to regenerator runtime #871

Async functions are always transformed to regenerator runtime #871

aocenas commented Feb 20, 2018 •

edited

Loading

aocenas commented Feb 20, 2018

devongovett commented Feb 20, 2018

aocenas commented Feb 20, 2018

davidnagli commented Feb 22, 2018

AbeEstrada commented Feb 23, 2018

silvestrevivo commented Mar 1, 2018

brandiqa commented Mar 3, 2018

silvestrevivo commented Mar 3, 2018

NullVoxPopuli commented May 3, 2018 •

edited

Loading

theoutlander commented May 17, 2018 •

edited

Loading

janat08 commented Sep 10, 2018

wesbos commented Jan 9, 2019

thedamon commented Jan 10, 2019

gcv commented Jan 13, 2019

Cody0913 commented Jan 22, 2019

thedamon commented Jan 23, 2019

shandou commented Feb 4, 2019

adrianmcli commented Feb 10, 2019

MarvelousWololo commented Jul 26, 2019 •

edited

Loading

adrianmcli commented Jul 29, 2019 •

edited

Loading

TempD commented Aug 1, 2019

wangcch commented Aug 28, 2019 •

edited

Loading

adrianmcli commented Aug 29, 2019

rosman21 commented Oct 14, 2019

corwin-of-amber commented Nov 7, 2019 •

edited

Loading

danielfilho commented Feb 2, 2020 •

edited

Loading

corwin-of-amber commented Feb 3, 2020

danielfilho commented Feb 3, 2020 •

edited

Loading

corwin-of-amber commented Feb 3, 2020

jcs224 commented Feb 25, 2020 •

edited

Loading

zavan commented May 13, 2020 •

edited

Loading

corwin-of-amber commented Nov 10, 2020

mischnic commented Nov 10, 2020

corwin-of-amber commented Nov 10, 2020

Async functions are always transformed to regenerator runtime #871

Async functions are always transformed to regenerator runtime #871

Comments

aocenas commented Feb 20, 2018 • edited Loading

🎛 Configuration (.babelrc, package.json, cli command)

🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution

🔦 Context

💻 Code Sample

🌍 Your Environment

aocenas commented Feb 20, 2018

devongovett commented Feb 20, 2018

aocenas commented Feb 20, 2018

davidnagli commented Feb 22, 2018

AbeEstrada commented Feb 23, 2018

silvestrevivo commented Mar 1, 2018

brandiqa commented Mar 3, 2018

silvestrevivo commented Mar 3, 2018

NullVoxPopuli commented May 3, 2018 • edited Loading

theoutlander commented May 17, 2018 • edited Loading

janat08 commented Sep 10, 2018

wesbos commented Jan 9, 2019

thedamon commented Jan 10, 2019

gcv commented Jan 13, 2019

Cody0913 commented Jan 22, 2019

thedamon commented Jan 23, 2019

shandou commented Feb 4, 2019

adrianmcli commented Feb 10, 2019

MarvelousWololo commented Jul 26, 2019 • edited Loading

adrianmcli commented Jul 29, 2019 • edited Loading

TempD commented Aug 1, 2019

wangcch commented Aug 28, 2019 • edited Loading

adrianmcli commented Aug 29, 2019

rosman21 commented Oct 14, 2019

corwin-of-amber commented Nov 7, 2019 • edited Loading

danielfilho commented Feb 2, 2020 • edited Loading

corwin-of-amber commented Feb 3, 2020

danielfilho commented Feb 3, 2020 • edited Loading

corwin-of-amber commented Feb 3, 2020

jcs224 commented Feb 25, 2020 • edited Loading

zavan commented May 13, 2020 • edited Loading

corwin-of-amber commented Nov 10, 2020

mischnic commented Nov 10, 2020

corwin-of-amber commented Nov 10, 2020

aocenas commented Feb 20, 2018 •

edited

Loading

NullVoxPopuli commented May 3, 2018 •

edited

Loading

theoutlander commented May 17, 2018 •

edited

Loading

MarvelousWololo commented Jul 26, 2019 •

edited

Loading

adrianmcli commented Jul 29, 2019 •

edited

Loading

wangcch commented Aug 28, 2019 •

edited

Loading

corwin-of-amber commented Nov 7, 2019 •

edited

Loading

danielfilho commented Feb 2, 2020 •

edited

Loading

danielfilho commented Feb 3, 2020 •

edited

Loading

jcs224 commented Feb 25, 2020 •

edited

Loading

zavan commented May 13, 2020 •

edited

Loading