grunt-phantomcss
grunt-phantomcss copied to clipboard
micahgodbolt
Installing in node_modules/@micahgodbolt
When I put this line in package.json:
"@micahgodbolt/grunt-phantomcss": "^0.4.0"
phantomcss installs in node_modules/@micahgodbolt/grunt-phantomcss, which requires loading it with this, instead of the line provided in the Readme:
grunt.loadNpmTasks('@micahgodbolt/grunt-phantomcss');
Can it be updated so that it installs in node_modules/grunt-phantomcss?
the @micahgodbolt is just the npm namespace. That is the correct way to load that module.
https://docs.npmjs.com/getting-started/scoped-packages
I also had this issue. The README for this project has:
grunt.loadNpmTasks('grunt-phantomcss');
yet in the comment above, you said the correct way to load the module is via
grunt.loadNpmTasks('@micahgodbolt/grunt-phantomcss');
Can you please confirm which of the two is the correct way? ... or perhaps they are equivalent? I have never used scoped packages so sorry if this is a case of RTFM.
@jameslawson no worries. Not a RTFM moment. I'm realizing that i've been using load-grunt-tasks for so long that I have never had to load a name spaced module by hand.
So first off, I'd highly suggest using load-grunt-tasks as it saves you a ton of headaches.
But if you want to do it manually, can you confirm that grunt.loadNpmTasks('@micahgodbolt/grunt-phantomcss'); works correctly? If so, I'll change the readme.
If you use: "@micahgodbolt/grunt-phantomcss": "^0.4.0" Then only this line will work: grunt.loadNpmTasks('@micahgodbolt/grunt-phantomcss');
If you use: "grunt-phantomcss": "git://github.com/micahgodbolt/grunt-phantomcss.git" Then you can use: grunt.loadNpmTasks('grunt-phantomcss');
When I try to install:
npm install @micahgodbolt/grunt-phantomcss --save-dev
I'm getting:
npm ERR! unregistered users are not allowed to access package @micahgodbolt/grunt-phantomcss : @micahgodbolt/grunt-phantomcss
Is that because we are using Sinopia proxy?
Why not making direct npm module? :\
