-
Notifications
You must be signed in to change notification settings - Fork 125
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
Unable to use with Vite in non-ember projects #2022
Comments
I think defining an exports key should also help resolve, which we'd probably want to align with modern package.jsons (provided it includes default and types) Additionally, we can specify for v1 addons to not use index.js via specifying ember-addon-main in ember-addon |
Yes, this I think is what prevents me from incorporating qunit-dom into every project I touch. |
Remove old files and dependencies from qunit-dom Add new test index.html that demonstrates the problem in mainmatter#2022 Fix exports Ah, so we do compile to ESM already We have to remove the ember-addon keyword because we don't want to provide an addon-main and then have a dependency on @embroider/addon-shim
Remove old files and dependencies from qunit-dom Add new test index.html that demonstrates the problem in mainmatter#2022 Fix exports Ah, so we do compile to ESM already We have to remove the ember-addon keyword because we don't want to provide an addon-main and then have a dependency on @embroider/addon-shim
#2028 is now merged, so we're only waiting for release now |
@sukima v 3.0.0-rc.1 should be installable and compatible with Vite 💪 |
Wowzers!
|
I'm now using the rc.2 release on https://limber.glimdown.com and https://tutorial.glimdown.com https://github.com/NullVoxPopuli/limber/blob/main/apps/repl/package.json#L123 🎉 To get the types resolved, I did need to change my tsconfig to extend from
So, I think for qunit-dom sanity, I'm going to PR some test projects that focus on the bare minimum to prove this stays working over time. |
Ran into an issue where the tsserver was unable to see the https://github.com/sukima/lit-app-starter-kit/tree/qunit-dom |
qunit-dom is still very |
Do you have moduleResolution set to bundler? I'm about to make some types test packages that show minimum required ts config |
After this is merged and released: #2065 compatibility with varying projects should be a bit more broad. |
I discovered a bug when following the instructions to install qunit-dom. I seems to expect Vite to include Broccollii with the bundled for browser output. I think this might have to do with the
package.json
not providing amain
and the defaultindex.js
is an ember-cli addon module.The basic premise was I had qunit working and I added qunit-dom like this:
package.json
devDependenciesimport ‘qunit-dom’;
to my test start up module (after first import of qunit)The console produces the following error:
Steps to reproduce
bun i
,npm i
,pnpm i
your preference I chose Bundev
scriptbun run dev
http://localhost:3000/tests/
This is the problematic commit: sukima/lit-app-starter-kit@42220f7
You can verify it is qunit-dom by
git checkout HEAD^
and running the steps above.The text was updated successfully, but these errors were encountered: