宣汉400电话办理【宣汉网站公司】宣汉百度优化、宣汉域名注册、宣汉网店美工、宣汉微信公众号托管

宣汉县隶属于四川省达州市，位于四川盆地东北大巴山南麓，地处渝川陕鄂结合部，是达州卫星城市，介于东经107°22′~108°32′，北纬31°06′~31°49′之间，县城距达州市区32公里、达州机场42公里，襄渝铁路和渝陕高速公路、达万高速公路、210国道穿境而过。 [1] 

宣汉县幅员面积4271平方公里，辖31个镇、19个乡、4个民族乡；2019年，户籍总人口127.82 万（常住人口102.3万），2019年，宣汉县实现地区生产总值3699090万元，人均地区生产总值36159元。 [2]  属中亚热带湿润季风气候区，无霜期长。境内地形复杂、山势逶迤，由东北向西南倾斜绵延。

宣汉县人文厚重。巴风土韵源远流长，境内罗家坝遗址，是巴文化的发源地；土家民俗风情独具，薅草锣鼓入选第一批国家级非物质文化遗产名录，是四川省唯一的土家族聚居地；红色文化底蕴深厚，创造了“一县成军（红三十三军）”的传奇，孕育了老一辈无产阶级革命家王维舟和新中国10位将军。 [1] 

宣汉资源富集；拥有巴山大峡谷，洋烈水乡等3个国家4A级旅游景区。矿产资源中天然气预计储量1.5万亿方，年拥有150亿立方的天然气产能和285万吨的硫磺产量，煤炭储量1.6亿吨，富锂钾卤水储量20.9亿方；农副产品资源丰富，是全国黄牛、木本药材、速丰林、茶叶生产基地和蜀宣花牛种源基地。 [1] 

2020年2月，四川省人民政府同意宣汉县退出贫困县。 [3]  2020年6月，宣汉成功创建为“四川省首批全域旅游示范区”。 [4]  2020年9月22日，荣获2019年度四川省粮食生产“丰收杯”。

Working with package.json

The best way to manage locally installed npm packages is to create a package.json file.

A package.json file:

• lists the packages that your project depends on.

• allows you to specify the versions of a package that your project can use using semantic versioning rules.

• makes your build reproducible, and therefore much easier to share with other developers.

Requirements

A package.json must have:

• "name"

• all lowercase

• one word, no spaces

• dashes and underscores allowed

• "version"

• in the form of x.x.x

• follows semver spec

For example:

{
  "name": "my-awesome-package",
  "version": "1.0.0"
}

Creating a package.json

There are two basic ways to create a package.json file.

1. Run a CLI questionnaire

To create a package.json with values that you supply, run:

> npm init

This will initiate a command line questionnaire that will conclude with the creation of a package.json in the directory in which you initiated the command.

2. Create a default package.json

To get a default package.json, run npm init with the --yes or -y flag:

> npm init --yes

This method will generate a default package.json using information extracted from the current directory.

> npm init --yes
Wrote to /home/ag_dubs/my_package/package.json:

{
  "name": "my_package",
  "description": "",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/ashleygwilliams/my_package.git"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/ashleygwilliams/my_package/issues"
  },
  "homepage": "https://github.com/ashleygwilliams/my_package"
}

• name: the current directory name

• version: always 1.0.0

• description: info from the readme, or an empty string ""

• main: always index.js

• scripts: by default creates an empty test script

• keywords: empty

• author: empty

• license: ISC

• bugs: info from the current directory, if present

• homepage: info from the current directory, if present

You can also set several config options for the init command. Some useful ones:

> npm set init.author.email "wombat@npmjs.com"
> npm set init.author.name "ag_dubs"
> npm set init.license "MIT"

NOTE:

If there is no description field in the package.json, npm uses the first line of the README.md or README instead. The description helps people find your package when searching npm, so it's definitely useful to make a custom description in the package.json to make your package easier to find.

How to Customize the package.json questionnaire

If you expect to create many package.json files, you might wish to customize the questions asked during the init process, so that the files always contain key information that you expect. You can customize the fields as well as the questions that are asked.

To do this, you create a custom .npm-init.js in your home directory ~/.npm-init.js.

A simple .npm-init.js might look something like this:

module.exports = {
  customField: 'Custom Field',
  otherCustomField: 'This field is really cool'
}

Running npm init with this file in your home directory would output a package.json that included these lines:

{
  customField: 'Custom Field',
  otherCustomField: 'This field is really cool'
}

You can also customize the questions by using the prompt function.

  module.exports = prompt("what's your favorite flavor of ice cream, buddy?", "I LIKE THEM ALL");

To learn more about how to create advanced customizations, check out the docs for init-package-json

Specifying Dependencies

To specify the packages your project depends on, you need to list the packages you'd like to use in your package.json file. There are 2 types of packages you can list:

• "dependencies": These packages are required by your application in production.

• "devDependencies": These packages are only needed for development and testing.

Manually editing your package.json

You can manually edit your package.json. You'll need to create an attribute in the package object called dependencies that points to an object. This object will hold attributes that name the packages you'd like to use. It will point to a semver expression that specifies the versions of that project that are compatible with your project.

If you have dependencies you only need to use during local development, follow the same instructions as above but use the attribute called devDependencies.

For example, the project below uses any version of the package my_dep that matches major version 1 in production and requires any version of the package my_test_framework that matches major version 3, but only for development:

{
  "name": "my_package",
  "version": "1.0.0",
  "dependencies": {
    "my_dep": "^1.0.0"
  },
  "devDependencies" : {
    "my_test_framework": "^3.1.0"
  }
}

The --save and --save-dev install flags

The easier (and more awesome) way to add dependencies to your package.json is to do so from the command line, flagging the npm install command with either --save or --save-dev, depending on how you'd like to use that dependency.

To add an entry to your package.json's dependencies:

npm install <package_name> --save

To add an entry to your package.json's devDependencies:

npm install <package_name> --save-dev

Managing dependency versions

npm uses Semantic Versioning, or, as we often refer to it, SemVer, to manage versions and ranges of versions of packages.

If you have a package.json file in your directory and you run npm install, npm will look at the dependencies that are listed in that file and download the latest versions, using semantic versioning.

Learn More

To understand more about the power of package.json, see the video "Installing npm packages locally" which you can find in Chapter 8.

To learn more about semantic versioning, see Getting Started "Semver" page.

宣汉400电话办理【宣汉网站公司】宣汉百度优化、宣汉域名注册、宣汉网店美工、宣汉微信公众号托管