07:18
<Sarath kumar>
HI, can anyone tell me how to design this type of card ?
07:26
<DerekNonGeneric>
the "design" is self-evident in the image; how it should be coded is probably off-topic
07:43
<DerekNonGeneric>
Sarath kumar: i do not understand your question.. it seems to have already been designed, no?
08:00
<Sarath kumar>
current design is like below, i have to modify the current design to the above one
08:01
<Andreu Botella (he/they)>
Sarath kumar: Hi, this chatroom is for working on the web standards, or for help understanding them. It's not for general help with web development.
08:02
<Andreu Botella (he/they)>
You might want to try asking in #webdevelopment:matrix.org or #webdesign:matrix.org
08:31
<DerekNonGeneric>
so is there an nvm syntax for “latest”?
there appears to be a way to acquire the latest version of node for github actions, but you have to define it in the manifest https://github.com/actions/setup-node/blob/38d90ce44d5275ad62cc48384b3d8a58c500bb5f/src/installer.ts#L53
08:32
sideshowbarker
there appears to be a way to acquire the latest version of node for github actions, but you have to define it in the manifest https://github.com/actions/setup-node/blob/38d90ce44d5275ad62cc48384b3d8a58c500bb5f/src/installer.ts#L53
looks now
08:33
<DerekNonGeneric>
unclear on what is meant by "manifest" here, but it is possible that they mean in the package.json file (engines.node key)
08:42
<DerekNonGeneric>
we do not use the term "manifest" in node core when referring to the package.json file at all, but have seen Yarn do so in their docs
09:05
<DerekNonGeneric>
probably going to end up setting up a test project to get this solved for my own purposes, but am surprised that this isn't more ergonomic
09:10
<sideshowbarker>
I guess I rightly should be setting the engines.node version to >=15.0.0 regardless — since that’s what’s required for using .replaceAll()
09:12
<DerekNonGeneric>
in reality, it should probably be >=16 since this release line will last you longer (wonder if setting this value to node does anything)
09:22
<sideshowbarker>
I can try setting it to node and see
09:23
<DerekNonGeneric>
you would still need to figure out what the github actions yaml file would need to look like in order for it to utilize the package.json tho (i think)
09:28
<sideshowbarker>
ah
10:16
<DerekNonGeneric>
* looks now
this part is documented here, so it looks like it is simply determining whether the version specified in the package.json is the latest x.x.x version: https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#check-latest-version
11:25
<DerekNonGeneric>
sideshowbarker: here it is my friend, all that needs to be done is to specify the version as x.x.x and ensure check-latest is set to true -- glad we got that squared away https://github.com/DerekNonGeneric/test-repo-please-ignore/blob/main/.github/workflows/build.yml
11:29
<sideshowbarker>
sideshowbarker: here it is my friend, all that needs to be done is to specify the version as x.x.x and ensure check-latest is set to true -- glad we got that squared away https://github.com/DerekNonGeneric/test-repo-please-ignore/blob/main/.github/workflows/build.yml
thanks much!
11:30
<DerekNonGeneric>
yw