Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Async load zxcvbn.js to use with ember-cli-password-strength

Open
#1,662 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start with ember-cli-build.js and the existing ember-stripe-elements addon/utils/load-script.js utility. Enable asynchronous loading for ember-cli-password-strength, then determine how the project should provide zxcvbn.js at a project-controlled path instead of the default root URL. Done means async mode is enabled and the library loads successfully without bundling it.

Written by the indexing model from the issue text.

Description

Difficulty: Medium Skill: JavaScript Time: 2 hours

Problem

ember-cli-password-strength, since 2.0.0, has support for asynchronous loading of the zxcvbn.js library.

Since the library is 400k gzipped, it would make sense for us to make use of this.

However, the addon does not provide a framework to actually include the library as part of the project. Instead, it assumes, if aync mode is on, that the library is locaded at ${config.rootUrl}/zxcvbn.js

We need to find a way to deal with this and switch to async mode.

Subtasks

  • Turn on async mode for the addon as per instructions, by modifying the app's ember-cli-build.js and adding
let app = new EmberAddon(defaults, {
  'ember-cli-password-strength': {
    bundleZxcvbn: false
  }
});
  • Provide the library, either at the expected path, or, more likely at our own path, by providing custom async loading facilities, similar to what we do with ember-stripe-elements

https://github.com/code-corps/ember-stripe-elements/blob/master/addon/utils/load-script.js

Dominant language
JavaScript
Stars
120
Forks
75
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.