Set up shared Prettier configuration from @upfluence/w-conf

[Copilot]

Introduces the shared Upfluence Prettier setup (@upfluence/w-conf) with import sorting, replacing the bespoke .prettierrc.

Changes

• prettier.config.mjs — New ESM config using buildConfiguration from @upfluence/w-conf/prettier, with sortImport scoped to @upfluence/hyperevents
• package.json — Added @upfluence/w-conf@^0.2.0, @trivago/prettier-plugin-sort-imports@^4.3.0; bumped prettier to ^3.0.0
• .prettierrc — Deleted (superseded by prettier.config.mjs)
• .prettierignore — Added pnpm-lock.yaml
• Reformatted files — Markdown, HBS templates, tsconfig.json, and HTML files updated to match new config output

// prettier.config.mjs
import { buildConfiguration } from '@upfluence/w-conf/prettier';

export default buildConfiguration({
  sortImport: {
    packages: ['@upfluence/hyperevents']
  }
});

What are the observable changes?

Running pnpm prettier --check . will pass. Import order in .js/.ts files is now enforced: Ember/Glimmer internals → third-party → @upfluence/hyperevents → relative.

🧑‍💻 Developer Heads Up

⚡ Since we are using Ember Octane now:

• Feel free to migrate existing components to Glimmer Components.
• Write new ones exclusively in it.

Useful Resource : Ember Octane vs Classic Cheat Sheet

Good PR checklist

• Title makes sense
• Is against the correct branch
• Only addresses one issue
• Properly assigned
• Added/updated tests
• Added/updated documentation
• Properly labeled

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/orgs/upfluence/packages/npm/w-conf/versions
  • Triggering command: /usr/bin/curl curl -H Authorization: ****** REDACTED (http block)
  • Triggering command: /usr/bin/curl curl -s -H Authorization: ****** REDACTED (http block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Summary

Set up the shared Prettier configuration from @upfluence/w-conf for this repository, following the same pattern as done in upfluence/identity-web#787 and already present in upfluence/hyperstream.

Changes required

1. Add prettier.config.mjs

Create a new file prettier.config.mjs at the root of the repository with the following content:

import { buildConfiguration } from '@upfluence/w-conf/prettier';

export default buildConfiguration({
  sortImport: {
    packages: ['@upfluence/hyperevents']
  }
});

The package name @upfluence/hyperevents comes from the "name" field in package.json.

2. Update package.json devDependencies

Add the following packages to devDependencies in package.json (they are not currently present):

• "@upfluence/w-conf": "^0.2.0"
• "@trivago/prettier-plugin-sort-imports": "^4.3.0"
• "prettier": "^3.0.0"

3. Run pnpm prettier --write

After adding the config file and installing dependencies, run:

pnpm prettier --write .

Commit all files reformatted by Prettier as part of this PR.

Notes

• The config file must use ESM syntax (import/export default) — do NOT use require/module.exports
• The file must be named prettier.config.mjs (not .prettierrc.js or prettier.config.js)
• Do not add a .prettierrc.js file — this repo doesn't have one to remove, just add the new .mjs config

This pull request was created from Copilot chat.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[aprentout]

Pre approved

[aprentout]

Question here, isn't it better to do the following ?

Suggested change

	import ActivityTracking from '../services/activity-tracking';
	import ActivityTracking from '@upfluence/hyperevents/services/activity-tracking';

[phndiaye]

doesn't change anything.
and it's actually better like this and it will also end up being relative imports when we land v2 addon format as the "package name as prefix" is part of Ember's weird magic ^^