it’s because of this line/lib https://github.com/mesqueeb/case-anything/blob/production/src/utils.ts#L7

ES6 does support unicode regexes so I’m trying to figure out the correct shadow config to support this for advanced compile

works fine in dev builds

using :output-feature-set :es-next doesn’t seem to help as I hoped

this seems to suggest that only /u style regexes are supported in ES6 https://stackoverflow.com/questions/280712/how-can-i-use-unicode-aware-regular-expressions-in-javascript

but I don’t understand how that lib could be generally used in that case

I’m not actually using that lib (it’s a transitive npm dep) so I could trying excluding it as a fix

or is there a way to exclude an npm source file (since I don’t need it)?

worst case I have to fork/override the lib but I’d prefer not to do that

hmm, case-anything is a dep of remirror which is the lib I need. I could also try excluding it there

@U0509NKGK something to watch out for if you are using remirror

thanks Steve! we've ended up going full tiptap 🙂

Ah yes, makes sense for a rum app

do you have the actual full error including stacktrace/location info?

the closure compiler is sometimes a little overeager when it comes to validating code

and sometimes complains about stuff that is actually perfectly valid

there don't seem to be any open issues currently https://github.com/google/closure-compiler/issues?q=is%3Aissue+is%3Aopen+Invalid+Regular+Expression

but that doesn't mean its not a bug

I’ll generate a full error now…..

Uncaught SyntaxError: Invalid regular expression: /^[a-zà -öø-ÿ]+|[A-ZÀ-ÖØ-ß][a-zà -öø-ÿ]+|[a-zà -öø-ÿ]+|[0-9]+|[A-ZÀ-ÖØ-ß]+(?![a-zà -öø-ÿ])/: Range out of order in character class (at main.js:3287:266)

when I look at that line in the generated js, it seems to be from the case-anything transitive npm dep

thats not a compiler error thats a runtime error

my suspicion in Google Closure as you say

which may just mean that its an encoding issue

do you set you page encoding properly?

true enough

<meta charset="utf-8"> in the head?

no I didn’t check that. will do now

thx

boom! that fixes it. once again you are a legend

much appreciated. I’m glad I only spent 3 hours before I decided to wait to ask you 🙂

😛

> define JS file I'm still a bit hazy on this I'm afraid. Ones that use const {x} = require('/something'); - you recommended this approach to me some time ago.

thats commonjs. its treated like node_modules files so less reliant on closure compiler rewriting

but also less friendly to reloading and stuff

I mean you are aware of how much more complicated hot-reload is in the JS world

Only superficially, and the most recent piece of knowledge that I have is that people from the React ecosystem have apparently figured out how to reload Reacts apps properly, without even losing any state. But that's probably not relevant here at all.

well, yes its possible. but it is much more complicated than just "eval this new code over the old one"

but yeah, shadow-cljs doesn't support reloading commonjs code at this time

I mean it attempts to but it is fairly limited

Right... Shame, page refreshing it is then. Thanks!