-
-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panel compile <path>
error: Could not resolve "./Calendar"
#7583
Comments
Try using the |
Not sure if I'm using it correctly: panel compile src/panel_full_calendar/main.py --build-dir src/
Running command: npm install
npm output:
added 7 packages, and audited 8 packages in 213ms
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
An error occurred while running esbuild: ✘ [ERROR] Could not resolve "./Calendar"
index.js:1:26:
1 │ import * as Calendar from "./Calendar"
╵ ~~~~~~~~~~~~
1 error |
The point was for you to be able to debug it by inspecting the contents of the build_dir. |
For a package you should really ask it to compile the dotted module paths ( |
Oh, magically it worked this time panel compile src/panel_full_calendar/main.py --build-dir src/
Building /Users/ahuang/repos/panel-full-calendar/src/panel_full_calendar/Calendar.bundle.js containing the following components:
- Calendar
Running command: npm install
npm output:
added 7 packages, and audited 8 packages in 2s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
esbuild output:
panel_full_calendar/Calendar.bundle.js 180.3kb
⚡ Done in 17ms But now I'm wondering, what do I do with this Calendar.bundle.js when I publish to PyPI? Do I need to add it to MANIFEST.in? |
I think MANIFEST.in is no longer needed with modern build tools, should be included by default by |
I wanted to compile: https://github.com/panel-extensions/panel-full-calendar/tree/main
The text was updated successfully, but these errors were encountered: