-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Bug: Failed to resolve entry for package "danfojs" #545
Comments
@devMagno you can check how it’s use for CRA here /~https://github.com/javascriptdata/Data-aRT |
Thanks! It worked for me, but I would really like to use Danfo for Vite :( |
Same here - rolled back to 1.1.1 - unfortunately that means I can't use parsing options in readExcel.... Unfortunately still breaks in Vite. |
Similar to issue #527 |
Also take a look at #514 |
Found a workaround on this thread: |
Aside from the workaround on the #525, I tried the #447 PR locally and it worked on Vite + React. Repro steps:
How I used the esbuild bundle version in my app: import { Button, Text } from '@mantine/core';
import * as dfd from '../../../danfo2/bundle.esm.js'; // place the file somewhere, in this case in my src dir
export default function Create() {
async function load_process_data() {
let df = await dfd.readCSV('/titanic.csv');
console.log(df.head().print());
console.log(df.ctypes.print());
const title = df['Name'].apply((x: string) => { return x.split(".")[0] }).values
df.addColumn("Name", title, {inplace: true});
console.log(df.head().print());
}
return (
<div>
<Text>Create</Text>
<Button onClick={load_process_data}>Load Data</Button>
</div>
);
} So based on these findings, we have to options.
Based on my |
Describe the bug
I've installed danfojs@^1.1.2 in my React project using Vite and I'm getting the following error:
I really don't know what to do, I tried googling the error and found nothing.
At first I thought it was a bug involving Vite, but then I tried using CRA and the bug still happens.
Screenshots

The text was updated successfully, but these errors were encountered: