|
Have you read this?
|
#
¿
Jan 30, 2014 18:41
|
|
|
|
| # ¿ May 4, 2024 11:19 |
|
|
It depends on how many entry points your app has, and which files each entry point needs on initial load. I'm a RequireJS fanatic, but it sounds like you're just concatenating and minifying everything together and loading it everywhere? In that case there's no big advantage except being ~part of the future~.
|
|
#
¿
Feb 27, 2014 09:59
|
|
|
My current secret weapon in the dependency management wars is nix, the all-encompassing package manager of pure functional doom.
|
|
#
¿
Oct 11, 2016 21:45
|
|
|
I have. I'm not sure what you're looking for. If you strip out all the optional bits, it's pretty straight-forward to hand-roll on both the front- and back-end. Don't do that, though; just look for your language(s) in the list of implementations on that site.
|
|
#
¿
Feb 21, 2017 23:06
|
|
|
Ellie, an embeddable jsfiddle-a-like for Elm. Even installs packages.
|
|
#
¿
Feb 26, 2017 02:01
|
|
|
Skandranon posted:I really don't like SSE because you can't actually attach a callback to ALL messages, you MUST subscribe to certain keys. This makes it hard to inspect the general stream and find out if the backend has a typo in the messages it is sending. I thought you could, with onmessage().
|
|
#
¿
May 30, 2017 17:24
|
|
|
|
| # ¿ May 4, 2024 11:19 |
|
|
quote:Calling npx <command> when <command> isn’t already in your $PATH will automatically install a package with that name from the npm registry for you, and invoke it. The related gif doesn't show a confirmation dialogue, so start registering your typosquatting packages now and brainstorming amusing things for them to do.
|
|
#
¿
Jul 11, 2017 22:34
|
|