Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Typescript migration #600
Typescript migration #600
Changes from all commits
c75999c
2c2c515
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
As suggested in #576 (comment) we need to declare the dependencies explicitly due to the
--no-autoinstall
flag in thebuild
script.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.
To be clear: even with autoinstall, dependencies would still be added to
package.json
, but automatically by parcel. IIRC it’s not quite compatible with workspaces and when starting from scratch you get overwhelmed with a ton of dependencies you’re not sure you even need, so I prefer to handle them manually.I don’t think
postcss
requires to be explicitly added, was it? I believe it’s already included (see yarn.lock) through parcel sub-dependencies.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.
The dependencies I added so far were required, otherwise it was throwing a "{module} not found" error. I don't know why it is throwing for
postcss
though. I will try to remove it and/or figure out why it is required.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.
No worries. I’m still experimenting / figuring out the whole workspaces and the best way to configure everything. Are you running scripts from the root or from
packages/emoji-mart
? If the latter, that might be why (and also maybe why you got around the typescript issue from #576). With workspaces, you need to handle dependencies from the root. Dependencies can still be added to a specific workspace (like it currently is), but there’s only onenode_modules
at the root. Workspaces install all workspaces dependencies at the root.We could even move all
devDependencies
to the rootpackage.json
if that helps with issues.