Dave on Nostr: #laravel I have to run "npm run build" after every javascript change to see the new ...
#laravel I have to run "npm run build" after every javascript change to see the new code run on the test-site instead of having a static JS file that is just always the latest version. I guess that's "modern".
Published at
2024-07-30 14:52:56Event JSON
{
"id": "a48bfdf3ec765e5cb9bd2a6c62c2a1acab3b882ca9f1ea571801f66c42300861",
"pubkey": "1e2637ad71db45378ad68094115f1128cd32bddb5d080ffd44f3518f4583cbfb",
"created_at": 1722351176,
"kind": 1,
"tags": [
[
"t",
"laravel"
],
[
"proxy",
"https://podcastindex.social/@dave/112876006679289159",
"web"
],
[
"proxy",
"https://podcastindex.social/users/dave/statuses/112876006679289159",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://podcastindex.social/users/dave/statuses/112876006679289159",
"pink.momostr"
],
[
"-"
]
],
"content": "#laravel I have to run \"npm run build\" after every javascript change to see the new code run on the test-site instead of having a static JS file that is just always the latest version. I guess that's \"modern\".",
"sig": "6eec38b631ee66b306b76b8d69331093effab8c15a9cbf2ab93dabe5a6d1a689f9e0d2c3af16923e09d6884bb8585ec3f134b3d164394da80167b881f96ed27f"
}
