Skip to content
This repository has been archived by the owner on Oct 9, 2020. It is now read-only.

How to fix 'Paths configuration XXX uses wildcards which are being deprecated for just leaving a trailing "/" to indicate folder paths.' and how to fix 'defaultJSExtensions configuration option is deprecated ...' #855

Open
ericnewton76 opened this issue Aug 7, 2018 · 0 comments

Comments

@ericnewton76
Copy link

ericnewton76 commented Aug 7, 2018

Given a config.js similar to:

System.config({
  defaultJSExtensions: true,
  transpiler: "plugin-babel",
  babelOptions: {
    "optional": [
      "runtime",
      "optimisation.modules.system"
    ]
  },
  paths: {
    "github:*": "jspm_packages/github/*",
    "npm:*": "jspm_packages/npm/*"
  },
  warnings: true,

  meta: {
    "*": {
      "babelOptions": {
        "react": true
      },
      "defaultExtension": "js"
    }
  },

  map: {
    "accounting": "npm:[email protected]",
    "babel": "npm:[email protected]",
    "babel-runtime": "npm:[email protected]",
    "core-js": "npm:[email protected]",
"---snip---":"--------------------snip-------------------------"
  }

I'm not sure how to fix this warning. Tried removing the wildcard from either side and both sides but still get either deprecation warning or failure to find package.

@ericnewton76 ericnewton76 changed the title How to fix 'Paths configuration XXX uses wildcards which are being deprecated for just leaving a trailing "/" to indicate folder paths.' How to fix 'Paths configuration XXX uses wildcards which are being deprecated for just leaving a trailing "/" to indicate folder paths.' and how to fix 'defaultJSExtensions configuration option is deprecated ...' Aug 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant