3 ms·
it is confusing the way you are explaining it, so much that even you can't understand. You do have a build step, you just think that doing that using node scri
by brazukadev 3mo ago
it is confusing the way you are explaining it, so much that even you can't understand.
You do have a build step, you just think that doing that using node script is the same as not having one, I guess.
- root_axis 3mo agoYeah, IMO they are just making stuff up. Even as explained what they're saying makes no sense. Ultimately, there needs to be some entrypoint into the client-side script, node has no built in way to serve source code it's type-stripped over http.
- austin-cheney 3mo agoIf Node is your web server then node does have a way to serve the code to the browser... or you could just have node write the stripped code to a file for your other web server. It sounds like you are not even trying to think through this. I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.
- root_axis 3mo ago> I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is. I recommend you stop making stuff up online. We're 10 layers deep into this thread and you still can't explain how any of this works in a coherent way. If any of this is real, why don't you attach a link from the node documention or an article that explains this technique that allows node to serve type stripped imports over http. I'm not asking for a link to the http stack, I'm asking you to explain how you run a node app that consumes your typescript source code and serves it over http without a bundler.
- brazukadev 3mo agoguy really think everybody is a JS-framework user so he can drop a few words and get away with saying things that doesn't make sense. But in the last post he kinda explained that he uses a node script to convert TS to JS. He is just confused.