@koumoul/vjsf 2.11.3 → 2.12.0-beta.2

package/.eslintignore

@@ -1,6 +1,9 @@
 /node_modules/
 /lib/utils/json-refs.js
 /dist
+/test-apps
+/coverage
+/stats.json
 /doc/.nuxt
 /doc/dist
-/coverage
+/doc/node_modules

package/.eslintrc.js

@@ -1,14 +1,18 @@
 module.exports = {
   root: true,
-  parserOptions: {
-    parser: 'babel-eslint',
-    sourceType: 'module'
+  env: {
+    browser: true
+  },
+  "globals": {
+    "expect": true
   },
   extends: [
     // https://github.com/feross/standard/blob/master/RULES.md#javascript-standard-style
     'standard',
-    // https://github.com/vuejs/eslint-plugin-vue,
-    'plugin:vue/recommended',
+    "plugin:vue/essential",
+    "eslint:recommended",
+    "standard",
+    "plugin:vue/recommended",
     'plugin:jest/recommended',
     'plugin:jest/style'
   ],
@@ -23,11 +27,12 @@ module.exports = {
     'no-debugger': process.env.NODE_ENV === 'production' ? 2 : 0,
     // This rule is required because atom vue-format package remove the space
     'space-before-function-paren': 0,
-    // Turn off vuejs rules, not because ther are not good, but mostly because
-    // they are very present in initial code base.. Maybe we should clean that up someday..
-    'vue/max-attributes-per-line': 'off',
-    'vue/require-prop-types': 'off',
-    'no-new': 'off',
-    'vue/no-v-html': 'off'
+    "vue/no-v-html": "off",
+    "vue/multi-word-component-names": "off",
+    "node/no-deprecated-api": "off",
+    "vue/no-mutating-props": "off",
+    "vue/require-prop-types": "off",
+    "vue/no-useless-template-attributes": "off",
+    "vue/singleline-html-element-content-newline": "off"
   }
-}
+}

package/CONTRIBUTE.md

@@ -18,7 +18,9 @@ Check all rules:
 
 Run a local development server:
 
-    npm run doc-dev
+    cd doc
+    npm install
+    npm run dev
 
 This simply opens the documentation site in a local web server that will watch your edits to the source code both of the library and of the documentation and its examples.
 
@@ -39,3 +41,21 @@ To increase efficiency test cases and documented examples are the same thing in
 When running tests each example is rendered and a HTML snapshot is extracted and compared to a previous one. When the tests fail because of a snapshot diff, you should check that it is a valid change, then run `npm run test-update`.
 
 You can also write additionnal test assertions in the examples themselves, see [_resolved-schema.js](./doc/examples/_resolved-schema.js) for example.
+
+## Publishing
+
+Release and publish usin npm:
+
+```
+npm version minor
+npm publish
+git push && git push --tags
+```
+
+To publish a beta version, use prerelease versioning with a npm tag:
+
+```
+npm version preminor --preid=beta # use prerelease instead of preminor to increment
+npm publish --tag=beta
+git push && git push --tags
+```

package/README.md

@@ -10,15 +10,6 @@ See [the documentation](https://koumoul-dev.github.io/vuetify-jsonschema-form/la
 
 ![](doc/static/vjsf.gif)
 
-## Development server
-
-The documentation serves as development server too.
-
-```
-npm install
-npm run doc-dev
-```
-
 ## Bug reports
 
 Bug reports are created using github issues. The examples in the documentation include codepen links, as much as possible please save a duplicate codepen with the minimal schema/config to reproduce your problem.

package/babel.config.js

@@ -0,0 +1,4 @@
+module.exports = {
+  presets: ['@babel/preset-env'],
+  plugins: ['@babel/plugin-transform-runtime']
+}