rollup | Rollup time-series data in Rails | Runtime Evironment library

Form npm install docs,

With the --production flag (or when the NODE_ENV environment variable is set to production), npm will not install modules listed in devDependencies

Since you have ENV NODE_ENV=production in your base image, neither rimraf nor parcel-bundler is installed inside your container.

Your npm start command is running npm run clean && npm run serve. npm run clean uses rimraf module and npm run serve uses parcel-bundler module. This is the reason why you're seeing both the errors.

You can try one of the following solutions,

1. Remove ENV NODE_ENV=production from your Dockerfile (This is the quickest solution but should not be used in production)

2. You can install rimraf and parcel-bundler globally inside the container using:

If we run with the idea that you ultimately want to leverage some existing code examples and therefore need data shaped like this :

This issue is due to a breaking change of svelte v3.29.5. So if you want to use this version you will also need to update rollup-plugin-svelte to at least v6.1.1.

The error message seems fairly straight-forward to me: the key size you used isn't supported by that library. In fact, you appear to have only pasted part of the message, which goes on to list the key sizes which are supported: https://github.com/phpseclib/phpseclib/blob/7e38313802b62606cf27ddf573a7c47e88b5d33f/phpseclib/Crypt/AES.php#L118

'Key of size ' . strlen($key) . ' not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported'

So your problem is not understanding what the PHP can do, but understanding what the JS is doing with your input.

The clue to that is in the CryptoJS docs:

CryptoJS supports AES-128, AES-192, and AES-256. It will pick the variant by the size of the key you pass in. If you use a passphrase, then it will generate a 256-bit key.

So the library agrees that there are three valid key lengths, but supports passing in a "passphrase" instead which will be used to generate a key. The exact algorithm it uses to do that isn't documented; presumably it uses some Key Derivation Function with fixed parameters, so that the same passphrase will always produce the same key. If you really need to emulate it, you'll need to trace through the source code.

If you just need code that's compatible with both libraries, generate a random key of one of the supported lengths, and use that in both places.

If you have tried reinstalling node modules and/or node overall:

The error seems to be with a lack of access to/from bash to the sirv command - which we can deduce from ENOENT (short for Error NO Entry). If you look at npm settings docs we can see how to configure which shell npm tries to use in running its scripts. I suspect if you ran npm config get script-shell you would get bash - which in the case of windows is referring to git bash specifically.

On my system with a working svelte example I have this set to null (which I did not set manually and weirdly isn't one of the options in the docs) so you can try to set it with npm config set script-shell=null or if that doesn't save your bacon try npm config set script-shell=cmd.exe.

You can easily achieve this result using reduce.

It's up to create-react-app maintainers to deal with this. The only thing you should do is to follow releases of "react-scripts" on github. So you would be up to date with fixes.

The only warnings you can fix are "peer dependencies" warnings ... You may install them ... or not :D

Try filling exports field in package.json. Documentation addresses the exact use case you describe:

Subpath exports

When using the "exports" field, custom subpaths can be defined along with the main entry point by treating the main entry point as the "." subpath:

I think a CTE and summary is probably a simpler method: