Timeline for Problem with @iota/client npm package in react app
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26 at 11:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 29 at 10:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 31 at 10:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 2, 2023 at 9:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 2, 2023 at 8:11 | answer | added | Jeroen van den Hout | timeline score: 0 | |
| Oct 1, 2023 at 20:51 | history | edited | mihi♦ | CC BY-SA 4.0 |
deleted 551 characters in body
|
| Oct 1, 2023 at 20:50 | comment | added | mihi♦ |
Can you share your package.json and package-lock.json files? Does it help if you delete node_modules/@iota and run npm install again? Looks like your client.js is an EXE file instead of JavaScript... That does not happen for me.
|
|
| S Oct 1, 2023 at 9:26 | review | First questions | |||
| Oct 15, 2023 at 9:34 | |||||
| S Oct 1, 2023 at 9:26 | history | asked | Sam Rouski | CC BY-SA 4.0 |