Allow config to blacklist packages from sort

[sandersky]

Overview

Does this PR close an existing issue?

Yes

Summary

Provide a general summary of the issue addressed in the title above

Issue Number(s)

• Closes Ability to ignore certain packages in sort order #33

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have evaluated if the README.md documentation needs to be updated
• I have evaluated if DocBlock headers needed to be added or updated
• I have verified that lint and tests pass locally with my changes
• If a fork of a dependent package had to be made to address the issue this PR closes:
  • I noted in the fork's README.md the reason the fork was created
  • I have opened an upstream issue detailing what was deficient about the dependency
  • I have opened an upstream PR addressing this deficiency
  • I have opened an issue in this repository to track this PR and schedule the removal of the usage of the fork

Semver

This project uses semver, please check the scope of this PR:

• #none#
• #patch#
• #minor#
• #major#

CHANGELOG

• Added ignore configuration for sort-import-declarations to ignore certain packages such as polyfills.

[sandersky]

@cstolli @sophypal I'm not sure how quickly Ciena engineers look at open source contributions or who to ping if need be on PR's so I'm tagging you both.

[sophypal]

@sandersky Just throwing out some questions to better understand the requirements. Is it required to have polyfills at the top? I was confused because I thought import order doesn't matter.

[sandersky]

@sophypal imports are hoisted to the top in the transpiled code but if you have something like the following:

import {fetchUsers} from 'awesome-api'
import 'fetch-polyfil'

awesome-api may operate on the assumption that window.fetch is defined as soon as it is loaded, which would happen before the polyfill loads. An example of how this might happen would be:

awesome-api

const {fetch} = window

export const fetchUsers = fetch.bind(null, '/users')

[sophypal]

@sandersky Thanks. I guess we never run into that here because polyfills are loaded before Ember's loader comes into play but that ultimately depends on how its shimmed and imported. Seeing as how this plugin isnt specific to Ember and you originally wrote it, I'll approve.