-
Notifications
You must be signed in to change notification settings - Fork 18
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
Feature/update packages #100
Feature/update packages #100
Conversation
sebastianrothe
commented
Feb 13, 2022
•
edited
Loading
edited
- Upgrade all packages
- Update e2e templates (svelte, sveltekit)
… be of type string. Received an instance of URL
src/transformer.js
Outdated
@@ -44,7 +55,7 @@ const processSync = (source, filename, jestOptions) => { | |||
const preprocessor = require.resolve('./preprocess.js') | |||
|
|||
const preprocessResult = execSync( | |||
`node --unhandled-rejections=strict --abort-on-uncaught-exception "${preprocessor}"`, | |||
`node --experimental-vm-modules --unhandled-rejections=strict --abort-on-uncaught-exception "${preprocessor}"`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this supposed to be in this PR? it looks like what you were trying to add in #101 instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got it a little bit mixed up :) I will move some of my commits to #101 instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or is it okay, because both go hand in hand?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this one seems better on #101 to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, i am going to move it.
these are all great updates! |
The PR queue got terribly backed up with dependabot alerts and the CI had broken due to bitrot. I fixed those issues not noticing this PR, so some of the updates have already gone in. A lot of the other changes in this PR look to duplicate #101, so probably we should review that one first and then see what's left that needs to be updated here It looks the like SvelteKit e2e example is very outdated as it's pre-1.0. It might be easiest to just create a new SvelteKit project and add |
Wow, thanks for the effort. And sorry, that I never found the time a year ago :( The e2e samples are really just generated. I had it document in the README. So they can b In my opinion, the #100 still needs to be cleaned from the mixup with #101. Good news is: I actually have some time this week, because I am going freelance. So I will push some PRs. If you can find the time to review, that would be great. Would love to bring Svelte4 support, afterwards. |
correct README
The path to the preprocessor was being used in the command with surrounding quotes, which lead to it failing when there is a space in the path with errors like this: ``` Test suite failed to run Command failed: node --unhandled-rejections=strict --abort-on-uncaught-exception D:\University\Year 4\<long path with more spaces>\node_modules\svelte-jester\dist\preprocess.js Uncaught Error: Cannot find module 'D:\University\Year' ``` This should fix the problem and allow for spaces in the path.
- v12 is supported until April 2022
- remove v12 - add v17 for CI
7baf450
to
e02f3d9
Compare
fix: add missing jest-environment-jsdom testing-library/svelte@4 requires ESM
@benmccann I have cleaned the PR from commits of #101 and refreshed the samples for svelte and sveltekit. |
TODO.md
Outdated
- add eslint with plugins (svelte, import, promise) | ||
- use different config loader https://github.com/unjs/c12 | ||
- use different build tool https://github.com/unjs/unbuild | ||
- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
empty bullet
- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, I accidentally commited my TODO list :)
TODO.md
Outdated
- use different config loader https://github.com/unjs/c12 | ||
- use different build tool https://github.com/unjs/unbuild | ||
- | ||
- add https://github.com/TrySound/rollup-plugin-terser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer unminified developer tools as it makes debugging them so much easier. Plus, npm has compression anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, thats true.
TODO.md
Outdated
- cleanup README | ||
- add eslint with plugins (svelte, import, promise) | ||
- use different config loader https://github.com/unjs/c12 | ||
- use different build tool https://github.com/unjs/unbuild |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that this project is using Rollup now. It's so common in the Svelte ecosystem it makes it really easy to pick up and start working on the project. I've never used unbuild on the otherhand. I think there's also some possibility we could ship unbundled ESM and don't even need a build tool at all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Im fine with rollup. The build tool is really just needed to convert ESM to CJS.