-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 ourterms of serviceand privacy statement.We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start to add node.js only parcel watcher wachman back-end #9789
base: v2
Are you sure you want to change the base?
Conversation
b00711b
to
5099a0d
Compare
"test:unit": "cross-env NODE_ENV=test mocha --timeout 5000 && cargo test", | ||
"test:integration": "yarn workspace @parcel/integration-tests test", | ||
"test:integration-ci": "yarn workspace @parcel/integration-tests test-ci", | ||
"test:unit": "lerna run build-ts && cross-env NODE_ENV=test mocha --timeout 5000 && cargo test", |
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.
You should be able to remove the explicitbuild-ts
(which is quite heavy handed) by modifying the parcel babel preset
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'd rather shift towards split compile and run lifecycle than the current mix of babel register etc.
It's quite confusing at the moment that there is the "dev" register mode and another mode that is pre-built (hence need the dev-prepare steps to fix-up the repository).
I'll just make it easy and use JSDoc syntax (?) |
Added a commit overv2...jondlm:parcel:jdlm-watchman-drop-in-replacement
Migrated to typescript but need to write some tests and integrate with the rest of the codebase.
The ignore patterns section likely is one thing that needs to be changed carefully though we could support only a subset of the current ignore options and delegate to watchman.