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

Copy unmaintained-text encoding polyfill locally #80

Conversation

cibernox
Copy link

@cibernox cibernox commented Jan 8, 2019

Closes #66

After reading the conversation in #66 seemed that creating a local copy of the deprecated polyfill is the simplest solution. Since the polyfill works fine I didn't like the idea of trying other polyfill that may differ in some subtle way.

This does not modify the license nor makes gives attribution to the original author or the polyfill, wich we should totally be done before this is merged, but I wanted to share this early and be sure it was an approach the maintainers of this library could be happy with.

Thoughts?

mantoni
mantoni previously approved these changes Feb 18, 2019
Copy link
Member

@mantoni mantoni left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@fatso83 fatso83 left a comment

Choose a reason for hiding this comment

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

Thanks for the work, but we need to do this a little bit differently. Having transpiled files makes it hard to do any changes, and we do module bundling anyway.

  1. Just copy everything in the main text-endoding repo into lib/text-encoding, except the package.json.
  2. Adjust the references to point to the right folder
  3. Make sure the tests for text-encoder still runs as part of the bigger test suite.

@fatso83
Copy link
Contributor

fatso83 commented Feb 18, 2019

@mantoni I see you already approved this, but do you disagree with my input? Having this part of the package should also include having it in a form that makes it suitable for maintenance (including tests).

@mantoni mantoni dismissed their stale review February 18, 2019 10:55

I agree with the points made by @fatso83

@fatso83
Copy link
Contributor

fatso83 commented Feb 18, 2019

Hold your horses, btw. I talked to @mantoni about this, which thought we should have an internal fork of the repo. I'll fix this asap.

@fatso83 fatso83 closed this Feb 18, 2019
@fatso83
Copy link
Contributor

fatso83 commented Feb 18, 2019

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.

3 participants