Timeline for PLACEHOLDER - NLN comment bot
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Apr 26, 2023 at 10:12 | history | suggested | user37421 | CC BY-SA 4.0 |
fix typo in title. removed unnecesary "PLACEHOLDER" label in question body.
|
Apr 26, 2023 at 8:23 | review | Suggested edits | |||
S Apr 26, 2023 at 10:12 | |||||
Jan 7, 2023 at 2:20 | history | edited | Ethan | CC BY-SA 4.0 |
added 148 characters in body
|
Jan 1, 2023 at 21:19 | comment | added | Ethan | @starball I was saying that node modules dont contain anything secret so there's no downside in committing. And I don't know. For this project Im coding directly in Replit so I don't want to change anything even though there is a history so I can rollback to a past version. | |
Jan 1, 2023 at 21:15 | comment | added | starball |
node_modules doesn't tend to contain any secret things as far as I'm aware, though I think some specific build tools like to store cache info in there IIRC. Does node_modules need to be committed for the replit to work? (I have never used it before). In general cases, committing node_modules can consume a lot of storage on your git repo host, and adds significantly to the time needed to clone the repo. If that's not relevant here, then that's fine.
|
|
Jan 1, 2023 at 21:12 | comment | added | Ethan | @starball im going to be using Replit to host it so I have been coding there and I just committed all the files without excluding any since it does not matter since all the secret stuff are stored in environment vars | |
Jan 1, 2023 at 20:47 | comment | added | starball |
Out of curiosity, did you commit :/node_modules on purpose? You already have package-lock.json in there.
|
|
Dec 12, 2022 at 14:38 | history | asked | Ethan | CC BY-SA 4.0 |