[DEV] Upgrade to Ember 6.1

[timjcook]

• Upgrade the addon to Ember 6.1 via ember-cli-update
  • Can't go further as ember-try fails for Ember 5.8 and below.
• migrated .eslintrc.js to eslint.config.mjs

[timjcook]

@antonivanopoulos @andybluntish I'm a little stuck on making a decision on these two imports. They are slightly different in nature.

For crypto, I believe what eslint is trying to tell me is that I can just call crypto without importing it on the version of node that I'm on, however I can't find supporting docs for that, most examples online continue to import like this.

For fetch, I believe eslint is aware that node ships with a fetch module, however this is using the installed node-fetch package, hence the namespace clash.

The thing that is really stopping me from making decisions is that there is no way to test this out, apart from pointing one of our apps at it and seeing if it works. While that would be effective, I kinda want to be more certain, especially as we are using private keys to sign things.

I'd like to write some tests but exporting a file from the lib dir into a test for an addon isn't straightforward. (lol at the supporting documentation for testing addons https://cli.emberjs.com/release/writing-addons/intro-tutorial/#testinganaddon).

Any thoughts would be valued.

[andybluntish]

The issue here is going to be the eslint setup. We're setting up the globals config to include globals.browser in all js files (**/*.{js,gjs}).

Later on we're including lib/**/*.js in the "node files" config, which adds the node globals, but this isn't overriding the previous config—is additive.

So eslint thinks that this file has access to both the browser and nodejs globals, and in this case is complaining that we're importing crypto because that exists in globals.browser.

For this plugin, we can probably just remove all the browser-specific eslint config, since there isn't any code that will run there.