transpile | Transpiles from everything to everything | Transpiler library

I do not see any issues with your code:

I am also stuck with the same problem because I installed the latest version of Node.js (v17.0.1).

Just go for node.js v14.18.1 and remove the latest version just use the stable version v14.18.1

The issue seems to be with using npm workspaces with Next.js... When I switched over to a minimal POC using yarn workspaces it seems to be working. Going to try to convert everything to using yarn now and see if it's all better afterwards, I'll update here once I do so.

Edit: Was able to successfully deploy the two apps now and I was able to import my common package from them.

Repo: https://github.com/saadq/proposals.es

thanks to @nalin-ranjan I've come up with the solution

in my "next.config.js" I added a rule to my webpack config:

I think the boring answer is that Babel only processes JavaScript files. Anything that's not JavaScript (e.g. JSON) gets left behind, even though it "feels" like the JSON file is a code dependency that Babel should "just do the right thing with" (since you required or imported it) -- or at least give you an error or a warning. But that is not how Babel was designed in this use-case.

You need to do extra work to copy data files. I suggest three main alternatives to choose from:

1. Use a bundler like WebPack or Gulp which has tools for copying non-JS files around
2. Use Babel's --copy-files which copies everything. You can sprinkle in --ignore patterns to try to avoid copying things you don't want copied.
3. Use something like the shx npm package which lets you run Unix-style filesystem commands in a cross-platform way from inside package.json scripts.

"build": "babel src --out-dir build && npx shx cp src/*.json dist/"

I recently answered a similar question, but there does seem to be a new issue introduced in 5.1.0 because of this change mentioned on the Bootstrap blog...

"Updated .bg- and .text- utilities Our new RGB values are built to help us make better use of CSS variables across the entire project. To start, our background-color and color utilities have been updated to use these new RGB values for real-time customization without recompiling Sass and on-the-fly transparency for any background or text color."

Currently in 5.1.0 you'd need to rebuild all the bg-* and text-* classes like this...

I had a similar problem but resolved by following steps.

1. Run the following command. heroku buildpacks:add heroku/nodejs --index 1
2. Update node version from 16.x to 12.16.2 in package.json.

Typescript is actually capable of doing this. See this explanation, I think it's very similar with your use-case.

I think your problem comes from the fact that you've defined the same variable payload in both switch-case branches. Either try to rename the payload in the second case, or just wrap your switch-case branches in curly brackets, { ... }.

Here's the code that works for me:

The documentation of the vue-splide integration is clearly talking about Vue3 composition API.

Checking in the github issues of vue-splide, I found this one which is referencing a solution that you've linked above. Meanwhile, when trying this, those are the warnings that I do have in my CLI.

Those are also related to Vue3 (which is not compatible with Nuxt2, only Nuxt3 supports Vue3). Looking at the date of all the posts, it looks like it was matching somewhat the time-frame when Vue3 was still in a beta-limbo and probably not adopted by everybody.

At some point, I guessed that the package maybe lost some retro-compatibility with Vue2 in the next months. I then tried to install the version 0.3.5 of @splidejs/vue-splide rather than the latest one and it's working perfectly fine with it!

Here is the whole setup to have it working with Nuxt2 nuxt.config.js