-
Notifications
You must be signed in to change notification settings - Fork 8
chore: REMOVE IMAGE_INLINE_SIZE_LIMIT variable #447
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
Conversation
|
Visit the preview URL for this PR (updated for commit 8b6903d): https://ccv-honeycomb--pr447-chore-inline-vl45atdq.web.app (expires Fri, 12 Apr 2024 19:37:47 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4ace1dcea913a952d2a1af84b94a4421bf36e610 |
eldu
left a comment
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.
Approving. I did add a comment, but nothing actionable really
.nvmrc
Outdated
| @@ -1 +1 @@ | |||
| v18.17.1 | |||
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 the sort of change I wouldn't expect in this PR. And instead in a PR that was about upgrading node.
But, I guess this is just some clean up after that fact?
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.
Hmm... I think the PR is out of date with feat-3.4, because I did have a separate pr for upgrading node
This is a stale environment variable that doesn't really matter? Images should be added to the
public/folder and jsPsych now respects that. We should be dealing with any users adding images tosrc/anymore.I know it makes for a few empty environment files but I think that's okay. I want to beef up the documentation of how to use the environment variables in which case have the "home" vs "clinic" is still pertinent