Lindera WASM UniDic Bundler is a JavaScript package providing a WebAssembly-based Japanese morphological analyzer, specifically pre-bundled with the UniDic dictionary. It is optimized for use within environments where JavaScript bundlers (like Webpack, Rollup, Parcel) are employed, typically targeting web browsers. The library provides capabilities for tokenization and detailed linguistic analysis of Japanese text. The current stable major version is `3.x.x`, with `3.0.5` being a recent release at the time of writing. Releases are made on an as-needed basis, often driven by Rust dependency updates or bug fixes. A key differentiator within the Lindera ecosystem is its explicit targeting of different environments (web, Node.js, bundler) and its flexibility in dictionary choice, making this package suitable for web applications requiring Japanese text processing.
npm install lindera-wasm-unidic-bundlerVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to initialize the WASM module and perform basic Japanese morphological analysis using the UniDic dictionary.
Migrate to the appropriate package (e.g., `lindera-wasm-unidic-web` for direct browser usage without a bundler, `lindera-wasm-unidic-nodejs` for pure Node.js environments leveraging NAPI-RS bindings, or `lindera-wasm-unidic-bundler` for bundler-processed web apps).
Always call `await init();` at the start of your application logic that depends on Lindera.
Ensure `builder.setDictionary("embedded://unidic");` is called when configuring the tokenizer for this package.For pure Node.js applications, use `lindera-wasm-unidic-nodejs` instead of `lindera-wasm-unidic-bundler`.
Ensure that `await init();` has completed successfully before creating a `TokenizerBuilder` instance.
Verify that `builder.setDictionary("embedded://unidic");` is correctly specified, as this package contains the UniDic dictionary. Also, check that `await init()` completed successfully.For Node.js environments, use the `lindera-wasm-unidic-nodejs` package, which is specifically built with NAPI-RS for Node.js compatibility and does not rely on browser-specific APIs.
No dependency data recorded yet.