Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export ES6 from js-sdk #817

Closed
wants to merge 4 commits into from
Closed

Export ES6 from js-sdk #817

wants to merge 4 commits into from

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Jan 7, 2019

This is a somewhat experimental PR to make the build process target
ES6 rather than ES5 given ES6 is now widely supported.

#803

This is a somewhat experimental PR to make the build process target
ES6 rather than ES5 given ES6 is now widely supported.

#803
package.json Outdated
"watchify": "^3.11.0"
"uglify-es": "^3.3.9",
"watchify": "^3.11.0",
"webpack": "^4.28.3",
Copy link
Collaborator

@jryans jryans Jan 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this package actually use Webpack? It's added here, but it doesn't seem like it's used before or after your changes.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, no it doesn't but I forgot to remove it.

dbkr added 2 commits January 7, 2019 19:13
babel-eslint is no longer necessary: ESLint now supports what we
need (in this case it was trailing commas). Fix lint errors with a
mix of updating lint rules to match our style, minor code fixes
and one ignore (I can't see whay it dislikes this one and not the
one above...)
@dbkr
Copy link
Member Author

dbkr commented Jan 8, 2019

Tests are currently failing because mocha is exiting with status 1 for no reason. Sigh.

as the promise in question isn't a bluebird promise and for some
reason this matters now where we got away with it before.
@dbkr
Copy link
Member Author

dbkr commented Jan 8, 2019

Fixed one error but it's still unhappy about the abuses we're committing in order to do inheritance in an ES5 world. We probably need to either find the specific thing we're doing wrong here or bite the bullet & port it to real classes.

@t3chguy
Copy link
Member

t3chguy commented May 10, 2022

@dbkr is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants