Update jupyterlite and enable file-system access

[martinRenou]

Also use comlink for the worker communication, like jupyterlite does with Pyolite.

Fixes #26

[martinRenou]

@bollwyvl May I kindly ask some help on the webpack+worker setup?

Webpack seems to not be processing the worker content properly when it comes to importing comlink and drivefs in the worker.

It fails with

bootstrap:19 Uncaught (in promise) TypeError: __webpack_modules__[moduleId] is not a function
    at __webpack_require__ (bootstrap:19:1)
    at ./lib/worker.js (lib_worker_js.94424d5a23f79f89129e.js:12:65)
    at __webpack_require__ (bootstrap:19:1)
    at bootstrap:34:1
    at __webpack_require__.O (chunk loaded:23:1)
    at __webpack_require__.x (bootstrap:35:1)

Webpack generates the following code:

/******/ (() => { // webpackBootstrap
/******/ 	"use strict";
/******/ 	var __webpack_modules__ = ({

/***/ "./lib/worker.js":
/*!***********************!*\
  !*** ./lib/worker.js ***!
  \***********************/
/***/ ((__unused_webpack_module, __webpack_exports__, __webpack_require__) => {

__webpack_require__.r(__webpack_exports__);
/* harmony import */ var comlink__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! comlink */ "webpack/sharing/consume/default/comlink/comlink");
/* harmony import */ var comlink__WEBPACK_IMPORTED_MODULE_0___default = /*#__PURE__*/__webpack_require__.n(comlink__WEBPACK_IMPORTED_MODULE_0__);
/* harmony import */ var _jupyterlite_contents__WEBPACK_IMPORTED_MODULE_1__ = __webpack_require__(/*! @jupyterlite/contents */ "webpack/sharing/consume/default/@jupyterlite/contents/@jupyterlite/contents");
/* harmony import */ var _jupyterlite_contents__WEBPACK_IMPORTED_MODULE_1___default = /*#__PURE__*/__webpack_require__.n(_jupyterlite_contents__WEBPACK_IMPORTED_MODULE_1__);
// Copyright (c) Thorsten Beier
// Copyright (c) JupyterLite Contributors
// Distributed under the terms of the Modified BSD License.

Weirdly, in JupyterLite, the way you set things up it does not generate something so similar:

"use strict";
(self["webpackChunk_JUPYTERLAB_CORE_OUTPUT"] = self["webpackChunk_JUPYTERLAB_CORE_OUTPUT"] || []).push([["packages_pyolite-kernel_lib_worker_js"],{

/***/ 88289:
/*!************************************************!*\
  !*** ../packages/pyolite-kernel/lib/worker.js ***!
  \************************************************/
/***/ ((__unused_webpack_module, __webpack_exports__, __webpack_require__) => {

__webpack_require__.r(__webpack_exports__);
/* harmony export */ __webpack_require__.d(__webpack_exports__, {
/* harmony export */   "PyoliteRemoteKernel": () => (/* binding */ PyoliteRemoteKernel)
/* harmony export */ });
/* harmony import */ var _jupyterlite_contents__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! @jupyterlite/contents */ 39694);
// Copyright (c) Jupyter Development Team.
// Distributed under the terms of the Modified BSD License.

Do you know what I could be missing? I tried using the worker-loader manually but failed to... I don't understand what you've done differently in JupyterLite when doing this.

[martinRenou]

Nevermind @bollwyvl, @trungleduc was able to help me. For some reason, adding a separate webpack setup for the worker fixes it.

Starting to have drive support in xeus-python as well 💯

[DerThorsten]

@martinRenou does it work to have a some fubar.py and import it if we add /drive/test to the pythonpath?
If so, we should add it to the pythonpath by default

[bollwyvl]

I've had fairly poor luck with ts-loader in the past, but glad that it's working out.

[martinRenou]

@DerThorsten idk! But we should definitely try that and see if that works.

@bollwyvl yeah.. I'd like to get rid of the TS-loader before merging. We should not need it.

[bollwyvl]

@DerThorsten <https://github.com/DerThorsten> idk! But we should definitely try that and see if that works.

And we get a shiny penny if alternative loaders like importnb work!

…

[martinRenou]

@martinRenou does it work to have a some fubar.py and import it if we add /drive/test to the pythonpath?
If so, we should add it to the pythonpath by default

Relative imports does work indeed! So we should add /drive/test to the pythonpath We actually don't need to do that I guess

[DerThorsten]

Jeah,you are right, relative imports are the proper thing in this case