When i try to npm start, error:
No configuration provided for .../main.scss, Error in plugin
"gulp-stylelint".
Someone help me!
The quickest way to add a configuration to stylelint is to extend one of the official shared configs:
stylelint-config-recommended
stylelint-config-standard
You should extend the standard config if you want stylelint to enforce stylistic conventions like spaces after colons in declarations and use the recommended config if you don't.
To use the standard config you should first install it as a devDependency:
npm install stylelint-config-standard --save-dev
Then create a configuration file, e.g. .stylelintrc.json, in the root of your project and add the following content to it:
{
"extends": "stylelint-config-standard"
}
Related
I've just tried updating to create-react-app 4, and have a ton of typescript eslint warnings, particularly
Missing return type on function #typescript-eslint/explicit-module-boundary-types
Is there any way to override these in a .eslintrc.json file for runtime?
I've currently got overrides that work there for my project when I explicitly execute
npm run lint
But when I use npm run start I get a ton of lint warnings that I can't seem to control.
Is there any way to do this?
It turns out there is a way to override the .eslint rules.
Create a .env file in your root, if you don't have one.
Add the following to it as a new line: EXTEND_ESLINT=true
Extend the lint rules in your favorite way. I use .eslintrc.json but other mechanisms exist
Now with that in place, have a look at the included rules from react, which live in
node_modules\eslint-config-react-app\index.js and copy the rules you like into your rules section.
You may also want to pay careful attention to the overrides section, examples of which you can see in the above file, and if you have js in your project, you may want to remove the default parser,
parser: 'babel-eslint'
and then only override for typescript files.
I did some research, but could not find a quick fix to this situation:
Vue-cli 3.4.0 - Webpack 4.29.0
My project does not have config/index.js as mentioned here.
I tried to open vue.config.js and disable eslint does not work.
I removed the cli-plugin-eslint package.
Don't have .eslintrc.js.
Could not find any other configuration about eslint in project.
--- Fix ---
I realize that I didn't control my settings well. It was built in vetur.
the easiest way to ignore eslint is to ignore the files you dont want to be linted. For example, create .eslintignore in your project root folder. then just add the following folder which you dont want to lint like,
add src\
I want to add this package to my project https://wikiki.github.io/form/tagsinput/
Based on the documentation
Installation
To install all extension:
npm install bulma-extensions
To install individual extension:
npm install bulma-[extensionName]
Intergration
Open your application's main .sass file and add the following line:
#import 'bulma';
#import '~bulma-[extensionName]';
And you good to go.
Note: You might need to add some changes in your nuxt.config.js for extra configuration.
This is my babelrc file. installed module-resolver and declared root and aliases.
actually this do works!! but underline annoying me... please click images below I cannot post images cause I'm new here.
[https://i.stack.imgur.com/ZzN5O.png]
warning like this - module is not installed i think intelliJ recognize it as module..
[https://i.stack.imgur.com/GTcWx.png]
I changed my root "./" -> "./src" but it didn't work.
I also installed eslint but don't know about that well I think that won't help this problem
has anyone solved this kind of issue before?
IDEA provides no special support for babel-resolver; please follow WEB-28241 for updates.
The problem is that there are dozens of plugins defining their own ways to resolve modules, we can't afford providing special support for all them... You can try using webpack aliases instead, or try a workaround from https://youtrack.jetbrains.com/issue/WEB-22717#focus=streamItem-27-1558931-0-0:
create a file config.js (you can use a different name if you like) in your project root dir
define your aliases there using the following syntax:
System.config({
"paths": {
"components/*": "./src/components/*"
}
});
components here is the alias you have defined in .babelrc
Now you can use imports like
import MyComponent from 'components/core/MyComponent';
in your code
According to http://www.slant.co/topics/1089/viewpoints/1/~what-are-the-best-client-side-javascript-module-loaders~browserify#9 one of the downside of using Browserify is that:
Not all javascript libraries have an npm version
While it's not too hard to create npm package for an existing library, it means maintaining it when the library updates. While most libraries are now on npm, many client side specific libraries are not.
I don't have any experience with npm aside from knowing how to install an existing module. In light of that, what is the easiest/best way to browserify with client-side non-npm libraries?
Is there a way for me to declare a local Javascript file as a dependency, instead of looking it up through npm?
You can use local modules without problems by two ways:
1.Use a relative path to a module in require:
var myModule = require('../js/my-module');
2.Use a module name, but before, you should to add it to browser property in package.json:
package.json:
...
browser: {
my-module: './js/my-module.js'
}
app.js:
var myModule = require('my-module');
Some packages are packages with bower, these can be used with browserify by using the debowerify plugin.
For non-versioned things you can copy them to a lib directory in your project or add them as a git submodule and then configure browserify so that it can find things there too.