npm
-
@apapadimoulis Tell us how you really feel.
-
@apapadimoulis said:
This is the result of throwing $10M at a bunch of San Francisco, JavaScript hacks with no experience writing any software, ever.
I'd be happy to write something good instead for just $9.8M :)
-
@flabdablet said:
There are predefined environment variables that point to these things.
%APPDATA%has the pathname of the root folder for per-user roamable application data, and%LOCALAPPDATA%has the pathname of the root folder for per-user per-workstation local application data. Using the first where you should have used the second is just sloppy.I would argue, rather, that the choice of names is sloppy. Of the two,
%APPDATA%is clearly "the default", and%LOCALAPPDATA%requires extra work and something extra to know about. If people aren't supposed to put stuff in the roaming profile by default, they shouldn't have made it the default. They could just as easily have had%APPDATA%be local application data, and%ROAMINGAPPDATA%be for roaming app data, no?
-
@flabdablet said:
And cmd still got used well after those were released, mainly because cmd scripts are way, way easier to debug and usually considerably more concise.
There's a
.cmddebugger? Link plx?
-
@Mason-Wheeler
%LOCALAPPDATA%was new in Windows Vista, so Microsoft needed to preserve the behaviour of%APPDATA%for backwards compatibility with programs designed for XP and earlier
-
-
@Mason-Wheeler said:
I would argue, rather, that the choice of names is sloppy. Of the two, %APPDATA% is clearly "the default",
Roaming *is *the default.
AppData has always been presumed to be settings files, not caches. Caches are the separate case which need to be treated specially.
@Mason-Wheeler said:
If people aren't supposed to put stuff in the roaming profile by default,
But people are supposed to. Just not stuff that can be easily re-created. (aka caches.)
EDIT: wow the italics button in the toolbar doesn't fucking work. Awesome job NodeBB, A++++. I'm always amazed to see these clowns get shit wrong that Discouse, of all software products, got correct.
-
-
@dkf said:
I'd be happy to write something good instead for just $9.8M
I'll even leave the Bay area! (rapidly)
-
@Mason-Wheeler said:
There's a .cmd debugger? Link plx?
echo on
(or@echo on)Meh, that's just tracing.
-
@blakeyrat said:
wow the italics button in the toolbar doesn't fucking work
Could you be more specific? It does something I would describe as "working" for me.
-
@ben_lubar said:
Could you be more specific?
Best I can do to replicate, use Shift+Ctrl+→ to highlight a word (and a space after the word), then press the formatting button, and you get what Blakey got.
-
-
@ChaosTheEternal Repro'd; it basically does this:
Some text and I'll *highlight *this and italicise it
when it should do this:
Some text and I'll *highlight* this and italicise itcc @ben_lubar
-
@Mason-Wheeler said:
They could just as easily have had %APPDATA% be local application data, and %ROAMINGAPPDATA% be for roaming app data, no?
That would fail the principle of greatest wtf that Microsoft used for names: system32, wow32.
-
@boomzilla said:
wow32
The stupid thing is if they'd used
w64ow32then the confusion would have never been there. Saving two characters: was it really worth it?
-
-
@dkf said:
The stupid thing is if they'd used w64ow32 then the confusion would have never been there. Saving two characters: was it really worth it?
Boomzilla got the name wrong. It's actually SysWow64. Already 8 characters.
Still your point is taken; it was a poorly-chosen name even given a 8-character limitation.
-
@dkf Actually, not quite. Because syswow64 contains the 32bit system32 binaries.
It stands for "Windows(32)OnWindows64".
System32 now contains the 64bit binaries.
So it's even more confusing than you lead on.
-
@Weng said:
So it's even more confusing than you lead on.
Obviously I'm one of the confused then.
Thanks Obama!
-
Just had to traverse a node_modules tree of epic proportions because dependencies in npm are not done through merely referencing the module and then using it.
No. If your module has a dependency it will pull that dependency into a sub-directory (regardless of whether that particular dependency has already been pulled in by another module)
So, now you have:
/module/node_modules/xyz-1.2.3/And if that module itself has dependencies...
/module/node_module/xyz-1.2.3/node_modules/abc-1.2.3/And so on and so forth. Im not quite sure which asinine thinking process prohibits simply putting all modules into the root-directory for npm and reference it from there.
The offender I ran into seemed to have 6 or 7 levels of sub-dependencies. Which I only discovered when I tried to prune the directory back from its 1 GB size (due to old versions) when Windows complained that the directory name was too long.
-
@Rhywden said:
Just had to traverse a node_modules tree of epic proportions because dependencies in npm 2 are not done through merely referencing the module and then using it.
They fixed it for npm 3, but you need to be using Node 5 to use that (I think it's available for some versions of Node 4 too)
-
@Rhywden I think there's some support in npm@2 for module reuse. But in any case, in npm@3, modules will be at the root level unless there's a dependency conflict.
The cost of all that? npm now takes 3x as long to do anything
-
@blakeyrat said in npm:
WSH had a full integrated development environment, including a graphical debugger.
Shame it doesn't ship with Windows by default, as everything you need to write and debug cmd scripts does.
-
One In Two New Npm Packages Is SEO Spam Right Now
More than half of all new packages that are currently (29 Mar 2023) being submitted to npm are SEO spam. That is - empty packages, with just a single README file that contains links to various malicious websites. https://datawrapper.dwcdn.net/ZkWKj/2...
-
@boomzilla said in npm:
One In Two New Npm Packages Is SEO Spam Right Now
More than half of all new packages that are currently (29 Mar 2023) being submitted to npm are SEO spam. That is - empty packages, with just a single README file that contains links to various malicious websites. https://datawrapper.dwcdn.net/ZkWKj/2...
Looks like more proof npm needs
-
@boomzilla said in npm:
One In Two New Npm Packages Is SEO Spam Right Now
More than half of all new packages that are currently (29 Mar 2023) being submitted to npm are SEO spam. That is - empty packages, with just a single README file that contains links to various malicious websites. https://datawrapper.dwcdn.net/ZkWKj/2...
Looks like more proof npm needs
It may well be possible.
antwas pretty well killed off by wrapping it and letting the inside die, andmavenis in turn being similarly displaced.However, the displacing tool will need to be excruciatingly shiny - written in Haskell compiled into WASM or something.
