keystonejs/keystone-classic

Adding `track` or `defaultSort` to any List breaks admin UI

Open

Aperta il 14 nov 2017

Vedi su GitHub
 (3 commenti) (1 reazione) (0 assegnatari)JavaScript (14.656 star) (2288 fork)batch import
bughelp wanted

Descrizione

Any ideas whatsoever would be great.

Expected behavior

I should be able to instantiate a new List with track or defaultSort set without an issue.

Actual/Current behavior

But for some reason, I get the following error on the /keystone/signin page:

signin.js:978 Uncaught TypeError: $export is not a function
    at Object.76../_descriptors (signin.js:978)
    at s (signin.js:1)
    at signin.js:1
    at Object.15.../../modules/_core (signin.js:83)
    at s (signin.js:1)
    at signin.js:1
    at Object.4.core-js/library/fn/object/define-property (signin.js:19)
    at s (signin.js:1)
    at signin.js:1
    at Object.48../_an-object (signin.js:610)

Steps to reproduce the actual/current behavior

Just add one of the aforementioned options to a List, old or new.

Environment

Software Version
Keystone 4.0.0-beta.7
Node 8.9.1

Babel config:

{
  "presets": [
    ["env", {
      "targets": {
        "node": "current"
      }
    }],
    ["stage-0"]
  ],
  "plugins": [
    "transform-runtime",
    "import-glob"
  ]
}

Guida contributor

Tech stack
javascriptnodejs
Dominio
full stack
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
JavaScriptKeystone classic basics
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
30
Direzione di ricerca
Investigate the error '$export is not a function' from core js. This likely indicates a module bundling issue triggered by adding 'track' or 'defaultSort' to a List. Examine the Keystone classic source code for List class initialization and how these options are processed. Also check the admin UI build configuration (babel and webpack) to see if the options cause a discrepancy in module imports. The issue is from 2017 and has few comments, so no clear resolution yet. Reproduction may require setting up a Keystone project with those options and debugging the client side bundle.