Closed taylorhadden closed 2 years ago
I has some issues with latest Webpack as well and finally got them resolved using:
rules: [
{
test: /\.js$/,
use: 'source-map-loader',
resolve: { fullySpecified: false }
},
{
test: /\.ts$/,
exclude: /node_modules/,
use: [{
loader: 'ts-loader',
options: { onlyCompileBundledFiles: true }
}],
},
I didn't understand how it helped, but fullySpecified
and onlyCompileBundledFiles
seemed to be important.
Does this help?
I'm really unhappy with the current state of bundlers. It seems there are issues with anything you use. I favored webpack over rollup because it worked with pretty much all modules and handles recursive imports, where rollup seemed to give me strife with every single project I tried to use it on. Now webpack does the same.
Thanks for the update; sorry for the long delay. I will check up on this soon.
"Soon" turned out to be relative; however, you're post was helpful.
I ended up using:
{
test: /\.js$/,
resolve: { fullySpecified: false }
}
And this solved my "path must be fully specified" problems.
I also very much agree regarding bundlers. I spent the last two days trying to get a Vite build working on Tangent, but esbuild
seems to be choking on export * from '@typewriter/delta'
and similar.
Seems like there is an open issue in esbuild for this... evanw/esbuild#1737
After updating my local repo of
typewriter-editor
to777a47d
, my project using Typewriter is failing to build.I'm getting dozens (hundreds? It overflows my console) of messages that look like this:
The built files for typewriter in my local repository look correct for an ES Module.
Am I just being a dummy and not configuring my project's Webpack to correctly load typewriter now that it's distributed as an ES2015 package?