-
Notifications
You must be signed in to change notification settings - Fork 128
Update page-lifecycle and y-indexeddb with tarball links #3262
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
Changes from 4 commits
2150149
431c8da
97874bf
40cbe6a
5eeece7
2e5cec6
5b14496
b0b2ff5
ecec300
b89243a
8e377d5
039cf33
73e28db
5facaa5
9b20df2
4f6b1d8
6a56822
aedf703
17c4404
ea48482
179726e
4b9f49a
c70a585
d9d3888
96b5000
0b62dab
4a363eb
67b42e0
c1c5d9b
07c03fa
6377356
5c52db7
10e8808
6d1674d
bd87d4c
23fcf9a
35d96a4
ce4cb89
a125460
99e792f
da95bbe
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -61,6 +61,7 @@ | |
| "workspace:" | ||
| ], | ||
| "allowed-hosts": [ | ||
| "codeload.github.com", | ||
| "github.com", | ||
| "npm", | ||
| "yarn" | ||
|
|
@@ -71,7 +72,9 @@ | |
| "resetMocks": false | ||
| }, | ||
| "resolutions": { | ||
| "@pandacss/node@npm:0.47.0": "patch:@pandacss/node@npm%3A0.47.0#~/.yarn/patches/@pandacss-node-npm-0.47.0.patch" | ||
| "@pandacss/node@npm:0.47.0": "patch:@pandacss/node@npm%3A0.47.0#~/.yarn/patches/@pandacss-node-npm-0.47.0.patch", | ||
| "page-lifecycle": "https://codeload.github.com/magic-akari/page-lifecycle/tar.gz/50b50421bdeab3d211a57e81a277f699638373b0", | ||
| "y-indexeddb": "https://codeload.github.com/raineorshine/y-indexeddb/tar.gz/60b960009085b1a988b5064ee35703229231531f" | ||
| }, | ||
| "workspaces": [ | ||
| "packages/*" | ||
|
|
@@ -110,7 +113,7 @@ | |
| "murmurhash3js": "^3.0.1", | ||
| "nanoid": "^5.1.5", | ||
| "openai": "^5.20.3", | ||
| "page-lifecycle": "git+https://github.com/magic-akari/page-lifecycle#feat/add-types", | ||
| "page-lifecycle": "^0.1.2", | ||
| "pluralize": "^8.0.0", | ||
| "qrcode.react": "^4.2.0", | ||
| "rc-slider": "^11.1.9", | ||
|
|
@@ -144,7 +147,7 @@ | |
| "workbox-strategies": "^7.3.0", | ||
| "workbox-window": "^7.3.0", | ||
| "xhtml-purifier": "^0.4.1", | ||
| "y-indexeddb": "https://github.com/raineorshine/y-indexeddb#y-indexeddb-multiplex", | ||
| "y-indexeddb": "^9.0.11-multiplex.0", | ||
|
||
| "y-protocols": "^1.0.6", | ||
| "yallist": "^5.0.0", | ||
| "yjs": "^13.6.27" | ||
|
|
||
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.
We actually need the
#feat/add-typesbranch from GoogleChromeLabs/page-lifecycle#12.v0.1.2is missing type definitions.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.
Would you check this part please?
I just replace with the version from the code.
https://github.com/magic-akari/page-lifecycle/blob/50b50421bdeab3d211a57e81a277f699638373b0/package.json#L3
And real reference is declared in
resolutionobject.This means the modules will be fetch from tarball link.
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.
Ahh, I forgot about resolutions! Do you know of any way to make this clearer for other developers? They might make the same mistake as me and not realize that it doesn't use the version listed in the package.json.
If resolutions overrides the package source, can we put any value there?
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.
What do you think about add special explanation in readme?
Regardless of what we put in dependencies, the resolutions value will be used.
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 README is too far away for it to be useful for this kind of thing. It needs to be co-located.
If the dependency value is ignored, I would recommend putting a dummy value that points to resolutions. I'm not sure if this is very conventional, but I can't think of a better way. It would be misleading otherwise.
Uh oh!
There was an error while loading. Please reload this page.
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.
What about removing values from resolution and use direct value into dependency values?
https://github.com/cybersemics/em/pull/3262/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R114
https://github.com/cybersemics/em/pull/3262/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R148
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.
That could work, though that just obscures it in the other direction, making it hard to know where the actual source code for the dependencies lives.