Closed davidbrochart closed 1 month ago
Should there be a new projects/jupyter-collaborativedrive
?
I'm wondering if this failure:
Error: src/yprovider.ts(6,35): error TS2307: Cannot find module '@jupyter/collaborativedrive' or its corresponding type declarations.
Error: src/ydrive.ts(16,8): error TS2307: Cannot find module '@jupyter/collaborativedrive' or its corresponding type declarations.
is caused by the fact that @jupyter/collaborativedrive
is not yet published to NPM?
I cannot reproduce it, it works locally.
@krassowski What do you think about getting this in before releasing v3?
We would need to publish @jupyter/collaborativedrive
to NPM.
@jtpio do you have the rights to publish @jupyter/collaborativedrive
to NPM?
@krassowski @jtpio ok to merge and publish @jupyter/collaborative-drive
?
I'm planning to merge today.
Thanks @davidbrochart. I'll try to have another look today.
Same error:
src/yprovider.ts:6:35 - error TS2307: Cannot find module '@jupyter/collaborative-drive' or its corresponding type declarations.
6 import { IDocumentProvider } from '@jupyter/collaborative-drive';
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I guess the published package is useless without code. I'll add jlpm build
back.
I guess the published package is useless without code.
What do you mean by "without code"? The package was published from this branch directly.
Oh my bad, yes the code is there. Then I don't know what is wrong.
Having to add jlpm run build
makes it look like something is wrong in the setup of the new package, since it was not needed before.
I guess the published package is useless without code.
What do you mean by "without code"? The package was published from this branch directly.
Actually yes, there is no code here.
I published @jupyter/collaborative-drive
v3.0.0-beta.7, and there is no IDocumentProvider
in lib/tokens.js
here. It is in lib/tokens.d.ts
but it's not enough, right?
In the end, I just think that jlpm build
is needed because the test in docprovider now needs @jupyter/collaborative-drive
through yprovider.ts, so it has to be compiled.
I'll take the risk to merge this PR and release jupyter-collaboration v3.0.0beta7. We can still revert the changes and release v3.0.0beta8 if it doesn't work.
Arf, I wanted to help you more on this yesterday but didn't have time.
At the very least it would have been great to leave a TODO, or open an issue...
Maybe check the tsconfig.json
to see if it needs a references
?
See https://github.com/jupyterlab/jupyter-collaboration/issues/352#issuecomment-2353809355.